Skip to main content
Glama

DunkAPI

Player games

get_player_games
Read-onlyIdempotent

Use for a player's game log: every game's box-score line with opponent and result, newest first, optionally one season. 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": {
      "player_id": "<player_id>"
    },
    "name": "get_player_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax games (default 100).
leagueNoLeague. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl.
offsetNo
seasonNoSeason by the year it ends: 2025 = 2024-25 (default: the latest).
player_idYesPlayer id.
season_typeNo

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
gamesYes
player_idYes
next_offsetNo

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. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / player_id / description
      Previous value: -"ESPN athlete id."New value: +"Player id."
  4. 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 readOnly/idempotent/non-destructive, so the description's job is additive — and it does add: ordering is "newest first" and the call "Costs 5 credits," which is genuine budget-relevant context absent from annotations. It stops short of describing pagination behavior or what happens past max offset, keeping it from a 5.

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?

One sentence, front-loaded with the use case, then the return shape, then ordering, then the optional filter, then cost. No redundant or filler wording.

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 values needn't be explained, and annotations cover the safety profile; the description adds the cost signal and sort order. The only real gap is pagination/offset semantics for a paged list 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 coverage is 67%, already above baseline, and the description reinforces the season parameter's semantics ("optionally one season") and the newest-first ordering implied by limit/offset. It adds nothing for offset or season_type, which remain undocumented in both places.

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 a specific resource and shape of result: "a player's game log: every game's box-score line with opponent and result, newest first." That distinguishes it from get_player (profile data) and get_game (one game) without naming them explicitly, so an agent can infer the boundary.

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 player's game log" plus "optionally one season" gives an implied when-to-use, but no explicit alternatives or exclusions are stated (e.g., use get_game for a single game, or that no date-range filter exists). Adequate but leaves routing to inference.

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.