Skip to main content
Glama

reports_view

View specific analysis reports by processing ID to access statistical insights, forecasts, and machine learning results from business data sources.

Instructions

View a specific report by processing ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
processing_idYesProcessing ID from tools_run

Implementation Reference

  • The tool 'reports_view' (along with all other tools) is handled by this dynamic proxy. It receives the request and forwards it to the remote client (api.mcpanalytics.ai).
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      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,
        };
      }
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'View' without clarifying safety (read-only), error conditions (e.g., invalid processing_id), return format, or that this retrieves results from an asynchronous operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at one sentence with no filler. However, it borders on underspecified given the lack of annotations and output schema—every word earns its place, but there are too few words to fully inform the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter retrieval tool with full schema coverage, the description is minimally adequate. However, given the implied workflow complexity (processing_id from tools_run suggests async job retrieval), the description should mention that this fetches results from a previously initiated report generation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents the processing_id parameter as coming 'from tools_run'. The description adds no additional semantics, syntax, or format details beyond repeating 'processing ID', warranting the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (View) and resource (report) and distinguishes this from sibling tools like reports_list or reports_search by specifying the lookup mechanism (processing ID). However, it misses the opportunity to clarify that this retrieves async results from tools_run.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives (e.g., reports_list for browsing). While the parameter description hints at a workflow with tools_run, the main description lacks explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/embeddedlayers/mcp-analytics'

If you have feedback or need assistance with the MCP directory API, please join our Discord server