Retrieves critical play situations like dangerous attacks, safe possession zones, and penalty pressure metrics. [CRITICAL]: Requires a valid matchId obtained from getEvents or getLiveEvents.
| Name | Required | Description | Default |
|---|---|---|---|
| matchId | Yes | The unique numeric ID. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It adds the critical dependency on a matchId from specific tools, which is useful. However, it does not disclose return format, behavior on invalid IDs, or confirm read-only status. It is adequate but leaves gaps.
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 tool's purpose and followed by a critical usage requirement. Every word adds value, with no filler or repetition.
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?
For a simple tool with one parameter and no output schema, the description covers the core purpose and a key prerequisite. It lists example return data but does not explain the structure or edge cases. Given the low complexity, this is reasonably complete but not exhaustive.
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 only describes matchId as 'The unique numeric ID.' The description adds that it must be a valid matchId obtained from getEvents or getLiveEvents, providing source and validation context beyond the schema. This meaningfully compensates for the schema's minimal description.
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 the tool retrieves 'critical play situations like dangerous attacks, safe possession zones, and penalty pressure metrics.' The verb 'retrieves' and specific examples make the purpose clear. It does not explicitly differentiate from siblings like get_match_timeline or get_match_stats, but the unique focus on 'critical play situations' provides enough distinction for a 4.
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 provides clear usage context by specifying that a valid matchId is required and that it must be obtained from getEvents or getLiveEvents. This gives the agent explicit guidance on prerequisites. It does not mention when not to use the tool or name alternatives, so it falls short of a 5.
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.