Skip to main content
Glama

DunkAPI

Leaders

get_leaders
Read-onlyIdempotent

Use for a season's statistical leaders (per game, shooting percentages with a volume floor, or totals) from every box score. Costs 5 credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
statYesStat to rank by.
limitNo
leagueNoLeague. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl.
seasonNoSeason by the year it ends: 2025 = 2024-25 (default: the latest).
min_gamesNoMinimum games played (default: a quarter of the season).
season_typeNoDefault regular.

Output Schema

NameRequiredDescriptionDefault
statYes
countYes
labelYes
seasonYes
leadersYes
min_gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nba. One of: nba, wnba, ncaam, ncaaw."New value: +"League. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nba",
      -  "wnba",
      -  "ncaam",
      -  "ncaaw"
      -]New value: +[
      +  "nba",
      +  "wnba",
      +  "ncaam",
      +  "ncaaw",
      +  "nbl"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds value beyond that by disclosing the 5-credit cost and the all-box-scores data source, both of which matter for planning and budgeting calls.

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

Conciseness5/5

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

Two sentences, no filler: the use case is front-loaded, the qualifier narrows scope, and the credit cost closes it out. Every clause carries information an agent needs.

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?

An output schema exists, so return shape needs no explanation, and annotations cover the safety profile. The description supplies scope, cost, and stat-family semantics; only the player-vs-team subject and default for limit are left implicit, both minor for a read-only ranking tool.

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

Parameters4/5

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

Schema description coverage is 83%, so the schema already documents most parameters and the baseline is 3. The description still adds meaning by explaining that the stat choice implies a mode (per-game vs shooting percentage with a volume floor vs raw totals), which clarifies the difference between enum values like pts and total_pts; min_games, season, league, limit and season_type are left to the schema.

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

Purpose4/5

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

Names a specific verb+resource pair: season statistical leaders drawn from every box score, and spells out the three stat families (per game, shooting percentages, totals) that the stat enum covers. It never explicitly says whether leaders are players or teams, which leaves a small ambiguity against the sibling get_team_stats.

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

Usage Guidelines3/5

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

The opening 'Use for a season's statistical leaders' gives a clear positive trigger, and the parenthetical narrows it to per-game, percentage, or total stat rankings. There is no when-not guidance and no sibling is named as an alternative, so an agent must infer that single-entity questions belong to get_player or get_team_stats.

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.