Skip to main content
Glama

Footalytics

list_fixtures

Upcoming football fixtures with fixture ids and a has_prediction flag (1 credit per successful call). Use it to discover matches, then call get_match_prediction with the fixture id or English team names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_fixtures"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional YYYY-MM-DD (UTC)
teamNoTeam name in English, e.g. Arsenal. Chinese names do not resolve.
limitNoOptional, default 20, max 50
leagueNoLeague filter: ESPN key (eng.1) or slug (premier-league). Known aliases such as 英超 work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two non-obvious traits: a cost of 1 credit per successful call and the shape of the returned fields. It omits auth requirements, empty-result behavior, and pagination semantics, but the credit pricing and return-content disclosure are meaningful additions.

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?

Two sentences, front-loaded with what the tool returns and the cost, followed by the workflow. No filler or redundant restatement.

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

Completeness4/5

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

For a four-parameter, optional-only read tool with no output schema and no annotations, the description covers purpose, returned fields, cost, and the follow-up call. The remaining gap is the absence of any mention of behavior when filters match nothing or of result volume relative to the limit parameter.

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 documents date, team, limit, and league filtering in detail. The description only repeats the English-team-name constraint already present in the team parameter, adding no new meaning; baseline 3 applies.

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?

States a specific verb and resource (upcoming football fixtures) and even names what the response contains (fixture ids and a has_prediction flag). The 'upcoming' qualifier implicitly separates it from list_results, though no sibling is explicitly contrasted by name.

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

Usage Guidelines4/5

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

Gives clear positive guidance ('use it to discover matches') plus an explicit handoff: call get_match_prediction with the fixture id or English team names. It does not state when not to use it (e.g. for finished matches, use list_results), so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources