Retrieves standings filtered specifically by recent overall, home, or away form. [CRITICAL]: Requires a valid seasonId obtained from getConfigTreeMini.
| Name | Required | Description | Default |
|---|---|---|---|
| seasonId | Yes | The unique numeric ID. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden. It discloses a critical dependency (seasonId from getConfigTreeMini) and states the filtering behavior. However, it does not describe the output format, what 'recent' means, or any other behavioral details, so it is adequate but not rich.
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?
The description is two sentences, front-loaded with the main action in the first sentence and a critical note in the second. No redundant information.
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?
Given the tool's simplicity (1 parameter, no output schema), the description covers the essential purpose and dependency. It would benefit from clarifying what 'form' means, but the combination of description and schema is sufficient for an agent to select and invoke it correctly.
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?
The schema describes seasonId only as 'The unique numeric ID,' but the description adds crucial semantics by specifying that it must be a valid seasonId obtained from getConfigTreeMini, guiding the agent on how to source the value. With 100% schema coverage, this extra context elevates the parameter understanding.
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 clearly states 'Retrieves standings filtered specifically by recent overall, home, or away form.' This identifies a specific action, resource (standings), and scope (form filtering), which distinguishes it from sibling tools like get_season_tables that likely return unfiltered standings.
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?
It gives a clear prerequisite: 'Requires a valid seasonId obtained from getConfigTreeMini,' telling the agent when it can use this tool (after obtaining seasonId). It does not explicitly name alternative tools or when-not-to-use, but the phrase 'filtered specifically' implies this is for form-based standings rather than general tables.
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.