Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nba_team_dash_pt_shots

Retrieve a team's NBA tracking shot dashboard to see shot breakdowns by touch time and shot type across selectable season, season type, and aggregation modes.

Instructions

Returns one team's tracking shot dashboard: the shot breakdowns the upstream computes for that team (by touch time and shot type), as several result sets. Returns one team's tracking shot dashboard: the shot breakdowns the upstream computes for that team (by touch time and shot type), as several result sets.

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": {
      "team_id": "<team_id>"
    },
    "name": "nba_team_dash_pt_shots"
  }
}

Input Schema

Name	Required	Description
`season`	No	Optional season in YYYY-YY form; defaults to the current NBA season.
`team_id`	Yes	Required team id from nba-standings.
`per_mode`	No	Optional aggregation.
`league_id`	No	Optional league id; only 00 (NBA) is verified.
`season_type`	No	Optional season type.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

C2.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a non-obvious trait: the response contains 'several result sets' rather than a single table, which matters for parsing. However, it says nothing about permissions, coverage limitations, or what the result sets are named or shaped like.

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

Conciseness2/5

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

The single sentence is repeated verbatim, doubling the length with zero added information. The underlying content is appropriately short, but the duplication signals a copy-paste error and wastes the agent's attention on the second pass.

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 five parameters, full schema coverage, and no output schema, the definition is minimally adequate: it names the domain and the breakdown dimensions. It stops short of describing the resulting tables or the season/per_mode interaction, which is the main thing an agent would still need to know before calling it.

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 three of five parameters carry enums, so the schema already documents season format, team id provenance, season type, and per_mode values. The description adds no parameter meaning beyond what the schema states, which lands at the baseline for fully covered schemas.

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 uses a specific verb and resource ('Returns one team's tracking shot dashboard') and names the content dimensions ('by touch time and shot type'), which lets an agent distinguish it from the player-level sibling. It does not name the closest alternatives (nba_team_pt_shot, nba_player_dash_pt_shots), so differentiation is implicit rather than explicit.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. An agent must infer from the phrase 'one team's' that this is the team-scoped counterpart of the player dashboard, and cannot tell from the description how this differs from nba_team_pt_shot or nba_opp_pt_shot.

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

Deploy Server