ReadMcpResourceTool: Read MCP Resources

The responsibility of ReadMcpResourceTool is very clear:
Given a server + uri, it reads back the body of the remote MCP resource.

Input definition:

export const inputSchema = z.object({
  server: z.string().describe('The MCP server name'),
  uri: z.string().describe('The resource URI to read'),
})

Actual reading goes through the MCP SDK:

const result = await connectedClient.client.request(
  {
    method: 'resources/read',
    params: { uri },
  },
  ReadResourceResultSchema,
)

There is a crucial snippet in the source code:

if (!('blob' in c) || typeof c.blob !== 'string') { ... }
const persisted = await persistBinaryContent(...)

This shows that it can handle not only text resources but also binary blobs, saving the content to a disk path before returning it.

Model receives MCP resource URI > ReadMcpResourceTool > verifies server is connected and supports resources > initiates resources/read request > returns text or blob > main thread continues processing the content

ReadMcpResourceTool imports external context into the main loop; it's a crucial step in truly implementing MCP integration.