Skip to main content
Glama

get_weekly_reports

Retrieve weekly market analysis reports from the Spanish stock exchange, including market overviews, sector breakdowns, and governance insights.

Instructions

Get generated weekly reports and analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportTypeNoType of report to filter by
limitNoMaximum number of reports

Implementation Reference

  • Core handler function that executes the tool logic by fetching weekly reports from the API endpoint '/api/reports'.
    async getWeeklyReports(reportType?: string, limit: number = 10): Promise<any[]> {
      const data = await this.fetchAPI('/api/reports', { 
        type: reportType, 
        limit: limit 
      });
      return data.reports || [];
    }
  • src/index.ts:316-334 (registration)
    Tool registration in ListToolsRequestHandler defining the tool name, description, and input schema.
    {
      name: 'get_weekly_reports',
      description: 'Get generated weekly reports and analysis',
      inputSchema: {
        type: 'object',
        properties: {
          reportType: {
            type: 'string',
            enum: ['market_overview', 'sector_analysis', 'governance_highlights', 'full_report'],
            description: 'Type of report to filter by',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of reports',
            default: 10,
          },
        },
      },
    },
  • MCP CallToolRequestHandler switch case that invokes the database handler with parsed arguments.
    case 'get_weekly_reports':
      result = await this.db.getWeeklyReports((args as any)?.reportType, (args as any)?.limit || 10);
      break;
  • Input schema definition for tool parameters (reportType and limit).
      reportType: {
        type: 'string',
        enum: ['market_overview', 'sector_analysis', 'governance_highlights', 'full_report'],
        description: 'Type of report to filter by',
      },
      limit: {
        type: 'number',
        description: 'Maximum number of reports',
        default: 10,
      },
    },
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. It mentions 'generated weekly reports and analysis' but doesn't specify whether this is a read-only operation, what permissions are needed, how data is returned (e.g., format, pagination), or any rate limits. For a tool with no annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to the purpose without redundancy or unnecessary elaboration.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavior, usage context, or output format. Without annotations or an output schema, more completeness would be beneficial, but it meets a basic threshold for a simple retrieval tool.

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?

The input schema has 100% description coverage, clearly documenting both parameters with enums and defaults. The description adds no additional meaning beyond the schema, such as explaining what 'weekly' entails or how 'analysis' is structured. With high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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 verb ('Get') and resource ('weekly reports and analysis'), making the purpose understandable. However, it doesn't differentiate this tool from similar siblings like 'generate_analyst_report' or 'get_historical_prices' that might also provide reports or data, leaving some ambiguity about its specific scope.

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 is provided on when to use this tool versus alternatives. With many sibling tools like 'generate_analyst_report' and 'get_historical_prices' that could overlap in providing reports or analyses, the description offers no context on prerequisites, typical use cases, or exclusions, leaving the agent to guess based on the tool name alone.

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/anbrme/ibex35-mcp-server'

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