Retrieve all FotMob FIFA ranking periods for a chosen gender, then use each returned periodId to fetch rankings via /fotmob/fifa-rankings.
FotMob FIFA ranking period directory. Returns every ranking period currently offered by FotMob for the selected gender. Use a returned periodId with /fotmob/fifa-rankings.
| Name | Required | Description | Default |
|---|---|---|---|
| gender | Yes | Ranking gender |
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 full burden. It implies a safe read-only directory and says it returns 'every' period, but discloses nothing about permissions, rate limits, or ordering. For a simple lookup this is adequate but thin.
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?
Three short sentences, front-loaded with the core purpose and ending with the actionable next step. No filler 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?
No output schema exists, so the description should describe the return shape; it conveys that a set of ranking periods (with periodId) is returned, which is sufficient for calling and chaining. Only a note on ordering or periodId format 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 the single gender enum is fully documented in the schema. The description's 'selected gender' phrasing mirrors the schema without adding format or defaulting detail, 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 and resource ('Returns every ranking period currently offered by FotMob') and scopes it to the selected gender. It is clearly distinguishable from the sibling fotmob_fifa_rankings by positioning itself as the period directory that feeds that endpoint.
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?
Explicitly tells the agent what to do next: 'Use a returned periodId with /fotmob/fifa-rankings.' This gives clear chaining context but contains no when-not-to-use or exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.