Retrieve all season values accepted by the FotMob league endpoint for one competition. Provide a numeric league id to list every valid season for that league.
FotMob league season discovery. Returns the complete list of season values accepted by the FotMob league endpoint for one competition.
| Name | Required | Description | Default |
|---|---|---|---|
| league_id | Yes | Numeric FotMob league id from /fotmob/leagues |
Changes observed during successful MCP inspections.
v1.17.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden, but it does convey this is a read-style enumeration (returns a complete list) and that the values feed the league endpoint. It omits auth requirements, ordering, and any pagination or caching behavior, which for a small discovery endpoint is acceptable 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?
Two sentences, purpose front-loaded, no filler or repetition. Efficient for the amount of information conveyed, though it stops short of adding anything beyond the minimum.
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 one-parameter discovery tool with no output schema and no annotations, the description adequately explains what is returned and how the result is consumed. Additional notes on ordering or emptiness handling would make it fully complete, but nothing essential for correct invocation is missing.
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% and there is a single parameter, so the schema already documents league_id with its source (/fotmob/leagues). The description adds no format, range, or lookup detail beyond that, so baseline 3 applies.
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?
States a specific verb+resource: discovering/listing the complete set of season values for one competition. It is clearly distinct in intent from fotmob_leagues and fotmob_league, but it never names those siblings or explicitly frames itself as a prerequisite step, so differentiation is inferential.
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?
By saying the returned values are 'accepted by the FotMob league endpoint,' it implies the tool is a lookup to run before calling the league endpoint, which is useful implied usage. However, there is no explicit when/when-not guidance and no named alternative, so usage is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.