Retrieve first-party ranking feeds for a selected category, including page two when page one fills, so you get all remaining ranking rows.
Flashscore rankings. Returns the first-party ranking feed pages for a supported ranking category. When page one is full, page two is included to cover the remaining rows.
| Name | Required | Description | Default |
|---|---|---|---|
| category | Yes | Ranking category from flashscore-ranking-categories |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It does disclose a non-obvious behavior: if page one is full, page two is included, so one call covers the full feed. The phrase 'first-party' also hints at data provenance. However, it does not describe the response format, error behavior, or any differences for live categories, so coverage is only partial.
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 first sentence 'Flashscore rankings.' is redundant with the tool name and could be removed. The remaining two sentences are efficient and front-loaded: the core purpose appears before the page-two nuance. Only one small waste keeps it from a 5.
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 read tool, the description is adequate but leaves gaps. It never defines what a 'ranking feed page' contains, does not mention that the category enum is sourced from flashscore_ranking_categories, and does not clarify the difference between regular and live categories. Since there is no output schema, the return shape is undocumented, though a valid enum value is enough to invoke it.
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 describes the category parameter with a full enum and a 'from flashscore-ranking-categories' note, so description coverage is 100%. The tool description adds nothing beyond 'for a supported ranking category', which just restates the schema. It does not explain the -live, -race, or -doubles suffixes, so it sits at the baseline 3.
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 ('Returns') and names the resource ('first-party ranking feed pages') with a clear scope ('for a supported ranking category'). The added detail about page two inclusion gives extra specificity. However, it does not explicitly differentiate from close siblings like flashscore_tournament_standings or flashscore_ranking_categories, so it stops short of a 5.
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 gives no guidance on when to use this tool versus alternatives. It does not mention that flashscore_ranking_categories provides valid category values, nor contrast with tournament standings or live ranking tools. There are no when-to-use or when-not-to-use cues, leaving the agent to infer selection from the tool name and enum alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.