Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nba_team_shot_locations

Retrieve an NBA team shot-location dashboard with one row per team and shooting stats by distance zone, using season filters and the verified By Zone range.

Instructions

NBA team shot-location dashboard. Returns the team shot-location dashboard: one row per team with the shooting columns for each distance zone. The endpoint requires both MeasureType and DistanceRange; a request without MeasureType answers HTTP 400 naming that parameter. distance_range is pinned to the one verified value, 'By Zone'.

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_team_shot_locations"
  }
}

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
`measure_type`	No	Statistic family
`distance_range`	No	Distance bucket set; only By Zone 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 does disclose useful behavior: MeasureType is mandatory at the endpoint and a missing value yields an HTTP 400 naming the parameter, and distance_range is pinned to the verified 'By Zone' value. It stops short of covering read-only safety, rate limits, auth, or pagination behavior.

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?

The return grain is front-loaded in the second sentence and the failure mode follows immediately, so the important facts come first. The opening phrase 'NBA team shot-location dashboard' is nearly restated by the following sentence, which is minor waste.

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?

With six parameters, no annotations, and no output schema, the description does the most valuable work by describing the return shape (one row per team, shooting columns per zone) and the 400 error. It does not explain how the optional season/season_type/league_id defaults combine, nor what the distance-zone columns are called.

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 coverage is 100%, so the baseline is 3; the description repeats the schema's verified-value notes (only 'By Zone' for distance_range, MeasureType required) without adding format or syntax detail. It also asserts both MeasureType and DistanceRange are required while the schema lists no required properties, leaving the agent to resolve that tension itself.

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 complement: a per-team dashboard of shooting columns by distance zone, with the return grain stated as 'one row per team'. It does not distinguish itself from close siblings such as nba_team_dash_pt_shots or nba_team_pt_shot, so an agent must infer the difference from the name.

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 is implied (team-level, zone-bucketed shooting splits) and the pinned distance_range value narrows the call, but nothing states when this should be chosen over the sibling shot tools or when it should not be used. No explicit alternatives or exclusions are offered.

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

Deploy Server