Fetches the master configuration tree of all global soccer categories (nations) and their corresponding tournaments. Use this tool to discover season IDs (seasonId) or tournament IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search or filter parameter. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only says 'Fetches the master configuration tree' but does not disclose any behavioral traits like output size, pagination, or whether it is read-only. This is a minor gap for a simple fetch tool.
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 action and resource, and includes a brief usage note. No unnecessary words 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 tool with one optional parameter and no output schema, the description gives a reasonable overview of purpose and use case. However, it lacks detail on the shape of the returned tree and how the query parameter affects results, leaving some ambiguity.
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 describes 'query' as 'Search or filter parameter' (100% coverage). The tool description adds a hint about discovering IDs, but it doesn't explain how to use the query parameter effectively. Thus, it provides marginal value beyond the schema.
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 uses a specific verb ('Fetches') and resource ('master configuration tree of all global soccer categories (nations) and their corresponding tournaments'). It clearly distinguishes this tool from sibling match/season tools by focusing on configuration discovery for IDs.
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 states 'Use this tool to discover season IDs (seasonId) or tournament IDs,' providing a clear use case. It doesn't mention exclusions or alternatives, but the context is sufficient for a simple config lookup tool.
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.