reports_view
Retrieve a previously generated report using its processing ID to view analysis results.
Instructions
View a specific report by processing ID.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| processing_id | Yes | Processing ID from tools_run |
Implementation Reference
- src/index.js:58-58 (schema)Static schema definition for the 'reports_view' tool. It requires a 'processing_id' string property. This is registered in the STATIC_TOOLS catalog as a fallback.
{ name: "reports_view", description: "View a specific report by processing ID.", inputSchema: { type: "object", properties: { processing_id: { type: "string", description: "Processing ID from tools_run" } }, required: ["processing_id"] } }, - src/index.js:117-119 (registration)The tool catalog (including reports_view) is exposed via the ListToolsRequestSchema handler, returning either the static or live-fetched catalog.
server.setRequestHandler(ListToolsRequestSchema, async () => { return { tools: toolCatalog }; }); - src/index.js:121-146 (handler)The execution handler for all tool calls including reports_view. It proxies the request to the remote MCP server (with the given name and arguments), or returns an error if no remote connection.
server.setRequestHandler(CallToolRequestSchema, async (request) => { if (!remoteClient) { return { content: [ { type: "text", text: "MCP Analytics API key required. Set MCP_ANALYTICS_API_KEY in your environment.\nGet a free key at https://app.mcpanalytics.ai", }, ], isError: true, }; } try { const result = await remoteClient.callTool({ name: request.params.name, arguments: request.params.arguments || {}, }); return result; } catch (err) { return { content: [{ type: "text", text: `Error: ${err.message}` }], isError: true, }; } });