Retrieves statistics detailing how often teams breach specific goal lines (e.g. Over 2.5 goals). [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?
Even though no annotations are present, the description discloses the read-only nature via 'Retrieves statistics' and adds a crucial behavioral constraint: the seasonId must come specifically from getConfigTreeMini. This goes beyond the schema's generic 'unique numeric ID' by revealing an external dependency and a validity requirement, giving the agent actionable understanding of how the tool behaves.
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. The first sentence immediately states the tool's purpose, and the second delivers an essential usage warning. Both sentences earn their place, making it efficient and front-loaded.
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 that there is no output schema and only one parameter, the description covers the tool's main purpose and the critical prerequisite. It could be more detailed about the exact statistics returned (e.g., percentages, team names), but the example 'Over 2.5 goals' provides enough context for an agent to understand the expected data type. Overall, it is adequate for a simple retrieval tool.
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 seasonId as 'The unique numeric ID', which is generic. The description significantly enriches this by specifying that the ID must be a valid seasonId obtained from getConfigTreeMini, thus providing the source and validity condition. Since schema coverage is 100%, baseline is 3, but the added source guidance raises it to a 4.
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 a specific action ('Retrieves statistics') and a well-defined resource ('how often teams breach specific goal lines'), with a concrete example (Over 2.5 goals). This distinguishes it from the many other season stats tools in the sibling list, such as get_season_goals or get_season_top_scorers, because it specifically targets over/under goal-line outcomes.
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 explicitly provides a usage prerequisite: it requires a valid seasonId from getConfigTreeMini, and even marks this as [CRITICAL]. This tells the agent when the tool is ready to be called (after obtaining seasonId) and which prior tool to use. It does not mention alternative tools or when to avoid this one, but the prerequisite is strong contextual guidance.
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.