Skip to main content
Glama

fixtures.list

Retrieve upcoming Serie A football matches within a specified number of days, including team details, kickoff times, and venue information for betting analysis.

Instructions

Ritorna i prossimi match di Serie A entro X giorni (id, squadre, kickoff, venue).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumero di giorni in avanti da scandire

Implementation Reference

  • The main handler function for the 'fixtures.list' tool. It calls the apiFootball client to get upcoming fixtures and returns a formatted JSON response.
    execute: async (args) => {
      const fixtures = await apiFootball.getUpcomingFixtures(args.days ?? 3);
      return JSON.stringify(
        {
          window_days: args.days ?? 3,
          fixtures,
        },
        null,
        2,
      );
    },
  • Helper method in ApiFootballClient that fetches upcoming Serie A fixtures within the specified number of days using the API, maps the response, and returns FixtureSummary array.
    public async getUpcomingFixtures(days: number): Promise<FixtureSummary[]> {
      const now = new Date();
      const from = toIsoDate(now);
      const to = new Date(now);
      to.setDate(now.getDate() + days);
    
      const params = {
        league: config.apiFootball.leagueId,
        season: config.apiFootball.season,
        from: from,
        to: toIsoDate(to),
      };
    
      const data = await this.get<FixtureResponse>("/fixtures", params);
      return data.response.map(mapFixtureSummary);
    }
  • Tool schema including name, description, and Zod input parameter schema for 'days'.
    name: "fixtures.list",
    description: "Ritorna i prossimi match di Serie A entro X giorni (id, squadre, kickoff, venue).",
    parameters: z.object({
      days: z.number().int().min(1).max(10).default(3).describe("Numero di giorni in avanti da scandire"),
    }),
  • The server.addTool call that registers the 'fixtures.list' tool within the registerFixturesTool function.
    server.addTool({
      name: "fixtures.list",
      description: "Ritorna i prossimi match di Serie A entro X giorni (id, squadre, kickoff, venue).",
      parameters: z.object({
        days: z.number().int().min(1).max(10).default(3).describe("Numero di giorni in avanti da scandire"),
      }),
      execute: async (args) => {
        const fixtures = await apiFootball.getUpcomingFixtures(args.days ?? 3);
        return JSON.stringify(
          {
            window_days: args.days ?? 3,
            fixtures,
          },
          null,
          2,
        );
      },
    });
  • src/index.ts:16-16 (registration)
    Invocation of registerFixturesTool on the MCP server instance, effectively registering the tool.
    registerFixturesTool(server);
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. The description states it returns match data, which suggests a read-only operation, but it doesn't address other behavioral aspects like rate limits, authentication needs, error conditions, or pagination. For a tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 extremely concise and front-loaded, consisting of a single sentence that efficiently conveys the tool's purpose, scope, and output. Every word earns its place, with no wasted information or redundancy. The structure is clear and direct, making it easy for an agent to parse quickly.

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 low complexity (one parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and output fields, but lacks details on behavioral traits, error handling, or usage context relative to siblings. Without annotations or output schema, the description should do more to compensate, but it provides just enough for a minimal viable understanding.

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 schema description coverage is 100%, with the 'days' parameter fully documented in the schema (type, range, default). The description adds marginal value by contextualizing 'X giorni' as the timeframe for upcoming matches, but it doesn't provide additional semantic details beyond what's in the schema. This meets the baseline score of 3 when schema coverage is high.

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's purpose: 'Ritorna i prossimi match di Serie A entro X giorni' (Returns upcoming Serie A matches within X days). It specifies the verb ('ritorna'), resource ('match di Serie A'), scope ('entro X giorni'), and output fields ('id, squadre, kickoff, venue'). However, it doesn't explicitly differentiate from sibling tools like 'match.snapshot' or 'odds.prematch', which prevents a perfect score.

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 minimal usage guidance. It implies the tool should be used when you need upcoming Serie A matches within a specified timeframe, but it doesn't mention when to use this tool versus alternatives like 'match.snapshot' or 'odds.prematch'. No exclusions, prerequisites, or explicit alternatives are provided, leaving the agent with little context for tool selection.

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/Valerio357/bet_mcp'

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