Fetch a FotMob league standings table by league ID to get all, home, away, form, and expected-goals views.
FotMob league table. Returns the league standings and the upstream table views, including all, home, away, form, and expected-goals tables. League ids are discoverable from /fotmob/leagues.
| Name | Required | Description | Default |
|---|---|---|---|
| league_id | Yes | Numeric FotMob league id |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full burden. It discloses what data is returned (standings and various table views), which is useful, but it doesn't mention that this is a read-only operation, any required permissions, or potential failure modes. The behavioral profile is adequate but has gaps.
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 three sentences, each serving a purpose: naming the resource, listing what's returned, and giving a discovery path. The first phrase 'FotMob league table' is slightly redundant with the tool name, but overall it's tight 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?
For a one-parameter tool with no output schema, this description covers the key information an agent needs: what the tool returns, the parameter, and how to obtain a valid value. It doesn't detail the return structure, but the description's enumeration of table views compensates reasonably.
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 by pointing to /fotmob/leagues as a way to discover valid league_id values, going beyond the schema's simple 'Numeric FotMob league id' description.
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 returns league standings and specific table views (all, home, away, form, expected-goals). This distinguishes it from siblings like fotmob_league or fotmob_matches, and the resource and action are unambiguous.
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?
It provides clear context: use when you need league standings or table views, and it tells the agent how to find league IDs via /fotmob/leagues. It doesn't explicitly state when not to use this tool compared to alternatives, but the context is sufficient for typical selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.