Retrieves the complete match calendar (past and future fixtures) for a team in a specific season.
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | The unique numeric ID. | |
| seasonId | Yes | The unique numeric ID. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavior. It clearly states this is a retrieval operation and specifies that both past and future fixtures are included. However, it omits potential details like pagination or ordering, though these are less critical for a simple two-param lookup.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that efficiently states the action, scope, and qualifier. No filler or redundant content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (two required params, no output schema), and the description adequately covers its purpose and result scope. 'Match calendar' reasonably implies a list of fixtures, so no significant gaps are evident for a retrieval tool of this size.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with both parameters described as 'The unique numeric ID.' The description adds the semantic that teamId and seasonId identify a team within a season, which is helpful but does not go beyond what the parameter names suggest.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Retrieves') and a precise resource: the complete match calendar for a team in a season. Naming 'past and future fixtures' distinguishes it from siblings that target only upcoming or past matches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (when a full team fixture list for a season is needed) but provides no explicit alternatives or exclusions. It does not name sibling tools like get_team_next_x or get_season_fixtures2.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes (e.g., timelines vs stats vs lineups), but there are several closely related match-stat and season-fixture tools that could be confused, such as get_match_stats vs get_detailed_match_stats vs get_match_details_extended.
All tools use a consistent get_ prefix and snake_case, but naming conventions vary in structure (e.g., get_season_fixtures2 vs get_livescore_season_fixtures) and one tool includes an arbitrary number suffix ('fixtures2'), which is a minor deviation.
With 41 tools, the server is significantly overscoped for typical MCP use. Although the soccer domain is broad, the sheer number of highly granular tools makes it heavy and harder to navigate.
The tool set covers nearly every aspect of soccer data: fixtures, live scores, match details, standings, top scorers, injuries, referees, team streaks, and more. Minor gaps exist, such as no direct team search or player match performance, but the surface is otherwise comprehensive.