Skip to main content
Glama

DunkAPI

Standings

get_standings
Read-onlyIdempotent

Use for a season's regular-season standings computed from every final game: overall, conference, home and away records, points for and against, margin and last 10. Costs 2 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_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl.
seasonNoSeason by the year it ends (default: the latest).

Output Schema

NameRequiredDescriptionDefault
noteYes
countYes
seasonYes
standingsYes

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the numbers are computed from every final game (derivation semantics) and the call costs 2 credits (a cost constraint). It does not mention latency or freshness, but with a rich annotation set this is above the bar.

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?

A single front-loaded sentence that leads with the use case, then the returned fields, then the credit cost. No filler or redundant restatement of the title.

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 an output schema present, the description needn't describe return values, and annotations cover safety. It adds the credit cost and the derivation basis, which is what an agent most needs. A small gap remains: nothing says whether teams with no completed games appear or how ties are ordered.

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 description coverage is 100% and both parameters (league enum with default, season-by-ending-year with default) are fully documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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?

The description names the resource (a season's regular-season standings) and enumerates the specific content returned: overall, conference, home/away records, points for/against, margin and last 10. That is far more specific than a tautology. It does not explicitly distinguish itself from the nearest sibling, get_team_stats, which likely also returns records, so it falls 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.

Usage Guidelines3/5

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

"Use for a season's regular-season standings" gives an implied context of use but never states when to prefer this over get_team_stats or get_ratings, nor any exclusions. An agent must infer the boundary from sibling names alone.

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.