26.0.0.3_beta

Author: IsmathBadsha

posts/2026-03-10-26.0.0.3-beta.adoc

@@ -36,18 +36,18 @@ See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta
 
 The link:https://modelcontextprotocol.io/docs/getting-started/intro[Model Context Protocol (MCP)] is an open standard that enables AI applications to access real-time information from external sources. The Liberty MCP Server feature (`mcpServer-1.0`) allows developers to expose the business logic of their applications, allowing it to be integrated into agentic AI workflows.
 
-When a client calls a tool, the object returned by the tool method is converted to a `ToolResponse`, which usually contains one or more `Content` objects. The `ToolResponse` maps directly to the result returned in the response.
+When a client calls a tool, the object that is returned by the tool method is converted to a `ToolResponse`, which usually contains one or more `Content` objects. The `ToolResponse` maps directly to the result returned in the response.
 
-If you need more control over the response from your tool, you can return a `ToolResponse` or `Content` object directly, but now it's also possible to register encoders to control how other objects are converted into a response.
+If you need more control over the response from your tool, you can return a `ToolResponse` or `Content` object directly. Now it is also possible to register encoders to control how other objects are converted into a response.
 
 * Use `ToolResponseEncoder` to convert an object into a `ToolResponse`, which gives you complete control over the whole response.
-* Use `ContentEncoder` when you only need to convert an object into a `Content` that will be included in the response. This also allows you to return a list of objects, and each object will be individually converted into a `Content` and included in the response.
+* Use `ContentEncoder` only when you need to convert an object into a `Content` that is included in the response. You can also return a list of objects, and each object is individually converted into a `Content` and included in the response.
 
-If a tool method returns an object for which no encoder is provided, JSON-B is used to encode the object as JSON which is returned as text content.
+If a tool method returns an object for which no encoder is provided, JSON-B encodes the object as JSON, which is returned as text content.
 
 === Example
 
-Say you have a tool which does a search over some datastore:
+Consider a tool which does a search over some datastore:
 
 [source,java]
 ----
@@ -58,11 +58,11 @@ public SearchResult search(@ToolArg(name="query", description="the query to run"
 }
 ----
 
-Imagine that the `SearchResult` object includes a list of results which includes a summary, some metadata, and an indication of how relevant the result is to the query.
+In this scenario, the `SearchResult` object encapsulates a list of individual results. Each entry contains a summary, associated metadata, and a relevance score that indicates its relationship to the query.
 
-By default, the returned `SearchResult` object will be encoded as JSON using JSON-B and the resulting JSON put into a `TextContent`. However, if instead we wanted each search result summary to be returned as its own `TextContent`, and set the priority annotation based on the relevance score, we can do that with a `ToolResponseEncoder`.
+By default, the `SearchResult` object that is returned is encoded as JSON by using JSON-B and placed into a `TextContent`. However, to return each search result summary as an individual `TextContent` and map the relevance score to a priority annotation, a `ToolResponseEncoder` is to be used
 
-Create a CDI bean which implements the `ToolResponseEncoder` interface and implement:
+Create a CDI bean that implements the `ToolResponseEncoder` interface and implement:
 
 * the `encode` method to create a `ToolResponse` from a `SearchResult`
 * the `supports` method to indicate that your encoder can be used for any `SearchResult`.
@@ -96,7 +96,7 @@ public class SearchResultEncoder implements ToolResponseEncoder<SearchResult> {
 }
 ----
 
-This encoder will be used for any tools in the application which return a `SearchResult`.
+This encoder is used for any tools in the application that return a `SearchResult`.
 
 // DO NOT MODIFY THIS LINE. </GHA-BLOG-TOPIC> 
 
@@ -107,9 +107,9 @@ This encoder will be used for any tools in the application which return a `Searc
 [#requestid]
 == Access the request ID from a tool
 
-Every request from an MCP client includes a Request ID which is unique to that session. Tools can now access that ID. This is mostly useful for logging or auditing.
+Each request from an MCP client includes a unique session-based Request ID, which is now accessible to tools and is useful for logging and auditing.
 
-To access the ID, simply add a `RequestId` parameter to the tool method:
+To access the ID, add a `RequestId` parameter to the tool method:
 
 [source,java]
 ----