Skip to main content
Glama

reports_list

Retrieve and manage analysis reports with metadata from business data sources like Shopify, Stripe, and Google Analytics. Filter results to find specific reports for statistical analysis and forecasting.

Instructions

List analysis reports with metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results

Implementation Reference

  • The tool execution is proxied to the remote MCP server via remoteClient.callTool. The 'reports_list' tool is dynamically fetched from the remote catalog and handled here at runtime.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List' implies a read-only operation, the description omits critical details like pagination behavior, what specific metadata is returned, rate limits, or authorization requirements given the lack of an output schema.

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

Conciseness3/5

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

The description is extremely concise at five words, but this brevity comes at the cost of omitting necessary context given the lack of annotations and output schema. While no words are wasted, the single sentence fails to earn its full keep by not addressing behavioral or return value questions.

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

Completeness2/5

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

Given the absence of annotations and output schema, the description should explain what data structure or metadata fields are returned. It mentions 'metadata' vaguely without specifying what information is included (e.g., creation date, author, size), leaving significant gaps for an agent trying to understand the tool's utility.

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?

With 100% schema description coverage ('Max results' for the limit parameter), the schema adequately documents the single parameter. The description adds no additional parameter context, but the baseline score of 3 is appropriate since the schema already provides complete coverage.

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 provides a clear verb ('List') and resource ('analysis reports') and adds specificity with 'with metadata'. However, it fails to distinguish this tool from siblings like 'reports_search' or 'reports_view', which could confuse the agent about when to list versus search or view specific reports.

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 offers no guidance on when to use this tool versus the related 'reports_search', 'reports_view', or 'report_cards' tools. There are no stated prerequisites, exclusions, or workflow context to help the agent select this over alternatives.

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