Retrieves the real-time live score status specifically mapped to a season's fixtures, useful for tracking live developments within a specific tournament. [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 full burden. It discloses that the tool returns real-time live scores and requires a valid seasonId, but does not detail response format, error behaviors, rate limits, or explicitly confirm read-only semantics beyond the verb 'retrieves'.
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 concise and front-loaded with two sentences. The first sentence states the purpose, and the second highlights a critical prerequisite. No filler or 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 low complexity (one parameter, no output schema), the description is mostly complete. It explains the purpose and the parameter source, but could briefly describe the return structure (e.g., a list of fixtures with live scores). However, the name and purpose provide strong implicit understanding.
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 provides 100% parameter coverage with a clear description of seasonId. The tool description adds valuable context by specifying that the seasonId must be a valid value obtained from getConfigTreeMini, which directly aids correct invocation.
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 real-time live score status mapped to a season's fixtures, using a specific verb and resource. It distinguishes itself from sibling tools like get_season_fixtures2 by emphasizing 'real-time live score status' rather than static fixtures.
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 a clear use case ('tracking live developments within a specific tournament') and explicitly states a critical prerequisite (valid seasonId from getConfigTreeMini). It does not name alternatives or exclusions, but the context is sufficiently clear.
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.