Retrieves general match statistics such as possession percentages, total shots, corners, and cards. [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 burden of behavioral disclosure. 'Retrieves' implies a read-only operation, and the CRITICAL note about matchId adds useful context about a dependency. However, it does not mention authentication, error behavior, or output format, leaving some 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 with no fluff. It front-loads the purpose and then adds the critical prerequisite, making it efficient and easy to scan.
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 single-parameter tool with no output schema, the description provides enough context: it lists example return data and the critical dependency on matchId. It could mention the return format more explicitly, but for a simple stats retrieval it is sufficiently complete.
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 already describes matchId as 'The unique numeric ID,' and the description adds meaningful context by specifying that it must be a valid matchId from getEvents or getLiveEvents. This goes beyond 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 general match statistics and lists specific examples (possession, shots, corners, cards). However, it does not explicitly distinguish itself from the sibling tool get_detailed_match_stats, relying on the word 'general' to imply scope.
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 explicitly states a prerequisite: matchId must be obtained from getEvents or getLiveEvents. This provides clear usage context, though it does not mention alternative tools or when not to use this one, so it doesn't reach 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.