Skip to main content
Glama

reports_list

List analysis reports with metadata to review historical analyses and access their details.

Instructions

List analysis reports with metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results

Implementation Reference

  • src/index.js:56-56 (registration)
    The tool 'reports_list' is registered in the STATIC_TOOLS array as part of the tool catalog. Its definition includes a name, description, and inputSchema (with an optional 'limit' parameter).
    { name: "reports_list", description: "List analysis reports with metadata.", inputSchema: { type: "object", properties: { limit: { type: "integer", description: "Max results", default: 10 } } } },
  • The actual handler for 'reports_list' (and all other tools) is the generic CallToolRequestSchema handler. It proxies the call to the remote MCP server via remoteClient.callTool(), passing the tool name and arguments. There is no local-specific handler for 'reports_list' — execution is delegated entirely to the remote API.
    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,
        };
      }
    });
  • The input schema for 'reports_list' defines a single optional parameter: 'limit' (integer, default 10).
    { name: "reports_list", description: "List analysis reports with metadata.", inputSchema: { type: "object", properties: { limit: { type: "integer", description: "Max results", default: 10 } } } },
  • The STATIC_TOOLS array serves as a fallback tool catalog used during inspection mode or when no API key is configured. It lists all available tools including 'reports_list'.
    const STATIC_TOOLS = [
Behavior2/5

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

No annotations are provided, and the description lacks disclosure of pagination, ordering, authentication needs, or data scope (e.g., all reports vs. user-specific). The tool could be a read operation but this is not clarified.

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

Conciseness5/5

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

A single sentence that is concise and front-loaded with the core action. No unnecessary words, perfectly sized for the tool's simplicity.

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 no output schema, the description should clarify what metadata is included. It is too brief for a tool with a single parameter and siblings, leaving the agent with insufficient context for correct invocation.

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 coverage is 100% with the 'limit' parameter already documented. The description adds no extra meaning beyond 'list with metadata', so it meets the baseline but does not enhance understanding.

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 tool lists analysis reports with metadata, using a specific verb and resource. However, it does not differentiate from sibling tools like 'reports_search' or 'reports_view', which could cause confusion.

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?

No guidance on when to use this tool versus alternatives. Siblings like 'reports_search' exist but no context is given for when listing is appropriate over searching or viewing.

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