Skip to main content
Glama

Leaders

get_leaders
Read-onlyIdempotent

Use for a season's leaders in goals, assists, goal contributions, shots, shots on target, our xG, cards, saves or clean sheets, as totals or per 90 minutes (per90, with a minimum of 10 matches by default). Costs 5 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
statNoDefault goals.
limitNo
per90NoRank by the rate per 90 minutes.
stageNoleague = league-table matches; knockout = qualifying, knockouts and playoffs; all. Default league, or all in the European cups.
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
seasonNoSeason by the year it starts (default: the latest).
min_gamesNoMinimum appearances.

Output Schema

NameRequiredDescriptionDefault
noteNo
statYes
countYes
labelYes
stageNo
seasonYes
leadersYes
min_gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / stage
      Added value: +{
      +  "description": "league = league-table matches; knockout = qualifying, knockouts and playoffs; all. Default league, or all in the European cups.",
      +  "enum": [
      +    "league",
      +    "knockout",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / stage
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context the annotations lack: a 5-credit cost and the implicit 10-match floor when per90 is used. Return shape is not described, but an output schema exists, so that is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the use case, with the cost noted at the end. The stat enumeration is long but each item is load-bearing for tool selection; no filler prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 optional parameters, an output schema, and rich annotations, the description only needs to supply defaults and cost, which it does for per90 and credits. It leaves the limit and stage default behavior entirely to the schema, a minor gap rather than a blocking one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the baseline is 3. The description restates the stat options and explains the per90 toggle plus the default minimum-games threshold, which is real added meaning since the schema lists min_games without a default. It says nothing about limit, stage defaults, or season format beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a precise resource (a season's statistical leaders) and enumerates the exact stat categories supported, so an agent can separate it from get_standings, get_team_stats, or get_player without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use for a season's leaders..." gives a clear triggering context plus the per90 variant and its default minimum. It stops short of naming when to prefer a sibling tool or any 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.