Retrieves detailed goals statistics for a season, including timing of goals, goal type distributions, and team scoring trends. [CRITICAL]: Requires a valid seasonId obtained from getConfigTreeMini.
| Name | Required | Description | Default |
|---|---|---|---|
| seasonId | Yes | The unique numeric ID of the season. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only operation through 'Retrieves' and lists some return content categories, but it does not describe the return format, possible errors, or the fact that an invalid seasonId would fail. This 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 core purpose in the first sentence and a critical usage note in the second. No redundant information; every word earns its place.
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 a single required parameter and no output schema, the description covers the for retrieving goals statistics, lists specific output dimensions, and provides a critical prerequisite. It lacks a full return structure description, but for a simple retrieval tool this is reasonably 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?
Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by specifying that the seasonId must be obtained from getConfigTreeMini, giving the parameter a source and validation context that the schema alone does not provide.
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 detailed goals statistics for a season and specifies the content types (timing of goals, goal type distributions, team scoring trends). This provides a specific verb and resource, distinguishing it from sibling tools like get_season_top_goals or get_season_team_scoring_conceding.
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 [CRITICAL] note gives explicit context on using a valid seasonId from getConfigTreeMini, which is a clear prerequisite. However, it does not mention when to choose this tool over alternatives or when not to use it, so it falls short of the full 5 benchmark.
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.