Retrieves the player leaderboard for most assists within a specific league season. [CRITICAL]: Requires a valid seasonId obtained from getConfigTreeMini.
| Name | Required | Description | Default |
|---|---|---|---|
| seasonId | Yes | The unique numeric ID of the season. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the operation is a retrieval (implying read-only) and includes a critical dependency on getConfigTreeMini. However, it lacks information about error handling, response format, or sorting order, which would enhance transparency.
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 a single sentence with a highlighted critical note. It is front-loaded with the core purpose, and the critical note is concise. 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 simple one-parameter tool with no output schema, the description is largely complete: it states the purpose and the essential prerequisite. It could mention that results are typically sorted descending by assists or include a note about seasonal scope, but these are minor gaps. Overall, it provides sufficient context for an agent to select and invoke the tool.
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 fully documents the seasonId parameter, so the baseline is 3. The description adds meaningful context by specifying that the seasonId must be obtained from getConfigTreeMini, which helps the agent source the correct value. This goes beyond the schema's simple type/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 retrieves the player leaderboard for most assists in a specific league season. The verb 'Retrieves' and resource 'player leaderboard for most assists' are specific, and the scope 'within a specific league season' distinguishes it from sibling tools like get_season_top_goals and get_season_top_cards.
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 provides clear context: the tool is for retrieving assists leaderboards for a season. It emphasizes a critical prerequisite that a valid seasonId must come from getConfigTreeMini, which guides usage. It does not explicitly name alternatives or exclusions, so it falls short of a 5.
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.