Skip to main content
Glama

DunkAPI

Ratings

get_ratings
Read-onlyIdempotent

Use for our team power ratings (Elo from every final game in our data), ranked, as of the end of a season or today. 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_ratings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTeams to return, best first (default 100; college has more than 300).
leagueNoLeague. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl.
seasonNoSeason by the year it ends (default: the latest).

Output Schema

NameRequiredDescriptionDefault
countYes
totalNo
methodYes
seasonYes
ratingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Teams to return, best first (default 100; college has more than 300).",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "type": "number"
      +}
  2. 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"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds genuinely new operational context: the cost ('Costs 2 credits') and the Elo derivation from final games, which tells the agent the numbers are not official standings.

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, front-loaded with the use case and followed by the cost. Nothing is redundant or wasted.

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, return values need no explanation, and all three optional parameters are covered by the schema. Cost and timing are stated; the only gap is the lack of explicit sibling routing for a tool sitting among several team-statistics alternatives.

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%, so limit, league, and season are already fully documented in the schema, including defaults and the season-end-year convention. The description adds the ranking direction ('best first' is in the schema) and timing ('today' vs end of season) but no new parameter-level detail, so the baseline holds.

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?

States a specific resource ('team power ratings'), the derivation ('Elo from every final game in our data'), and the ordering ('ranked'), so it is clearly distinct from get_standings or get_team_stats without naming them. It stops short of explicitly contrasting with those siblings.

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?

It gives a positive use case ('our team power ratings ... as of the end of a season or today'), which implies when to reach for it. But there is no explicit when-not guidance and no named alternative, even though get_standings and get_team_stats are obvious adjacent choices.

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.