Nba

Nba Get Player

nba_get_player

Read-onlyIdempotent

Direct lookup of a single NBA player by BallDontLie ID. ⚠️ TIER-GATED: the /players/{id} endpoint requires the ALL-STAR tier ($9.99/mo) or higher; free-tier _apiKey gets a 403 with "No approval received". search_players covers the same player metadata (name/position/height/weight/team) on the free tier, so prefer that unless you already have a paid BallDontLie key.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	BallDontLie player ID
`_apiKey`	Yes	BallDontLie API key

Output Schema

Name	Required	Description
`id`	Yes	Player ID
`name`	Yes	Full name (first + last)
`team`	Yes	Current team information
`height`	Yes	Player height
`weight`	Yes	Player weight
`college`	Yes	College attended
`country`	Yes	Country of origin
`position`	Yes	Player position
`draft_year`	Yes	Year drafted
`draft_round`	Yes	Draft round
`draft_number`	Yes	Draft pick number
`jersey_number`	Yes	Jersey number

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare this a safe idempotent read, but the description adds the critical non-schema behavior: the endpoint is tier-gated behind the ALL-STAR plan ($9.99/mo) and free-tier keys fail with a specific 403. That is auth/cost disclosure the agent cannot get from annotations or schema.

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, zero filler: the lookup scope comes first, then the gating constraint and the recommended alternative. The warning marker is justified because the constraint prevents a hard failure.

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

Completeness5/5

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

For a two-parameter, read-only lookup with a full output schema and clear annotations, the description covers everything an agent needs: what it returns conceptually, what credential tier is required, and which sibling to use instead if unqualified.

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 (id, _apiKey) are self-documented, so the baseline is 3. The description only reinforces that id is a BallDontLie-specific identifier and adds no format, range, or example beyond the schema's own example.

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?

States a specific verb and resource ('Direct lookup of a single NBA player by BallDontLie ID') and immediately contrasts it with the metadata-equivalent sibling search_players, so the agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use routing: prefer search_players on the free tier, use this only if you already hold a paid BallDontLie key. It also names the exact failure condition (403 'No approval received') that would otherwise waste a call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nba tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.