Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nba_pt_stats

Fetches the NBA player-tracking dashboard for the SpeedDistance measure by season, season type, league, and per-game mode, returning structured JSON player stats.

Instructions

NBA player-tracking dashboard. Returns the league player-tracking dashboard for one tracking measure. The endpoint rejects a trimmed query with HTTP 500, so the full dashboard scope set is always sent. pt_measure_type is pinned to the one verified measure, SpeedDistance.

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": "nba_pt_stats"
  }
}

Input Schema

Name	Required	Description
`season`	No	Season in YYYY-YY form; defaults to the current NBA season
`per_mode`	No	Aggregation
`league_id`	No	League id; only 00 (NBA) is verified
`season_type`	No	Season type
`pt_measure_type`	No	Tracking measure; only SpeedDistance is verified

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful hidden behavior: the endpoint returns HTTP 500 on a trimmed query, so the full scope set is always sent, and pt_measure_type is pinned. It says nothing about the shape or volume of the returned dashboard rows, so the behavioral picture is only partly filled in.

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

Conciseness4/5

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

Three short sentences, front-loaded with the resource before the operational constraints. The first two sentences overlap slightly ('player-tracking dashboard' restated as 'returns the league player-tracking dashboard'), but nothing is padding.

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

Completeness3/5

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

For a tool with five all-optional, fully documented parameters and no output schema, the description covers the invocation constraints but leaves the return content uncharacterized — an agent does not know which tracking metrics come back. Given the endpoint's fragility is already explained, this is adequate but not complete.

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 four of five parameters have enums, so the schema already documents everything. The description adds only marginal meaning, confirming that the enum restrictions (especially pt_measure_type) reflect what is actually verified rather than mere defaults.

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 verb and resource: 'Returns the league player-tracking dashboard for one tracking measure.' It is clear this is a league-wide tracking dashboard rather than shot-chart or hustle data, though it never names a sibling tool to route against (e.g. nba_pt_defend or nba_hustle_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?

Usage context is implied by 'player-tracking dashboard' and the note that only SpeedDistance is a verified measure, which tells an agent the scope is restricted. However, there is no explicit when-to-use/when-not-to-use guidance versus the many sibling pt_* tools, so the agent must infer selection.

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

Deploy Server