Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nba_team_dash_pt_pass

Fetches a team's passing dashboard and returns pass-type breakdowns as multiple result sets; requires a team ID and supports season, mode, league, and season-type filters.

Instructions

Returns one team's passing dashboard: the pass-type breakdowns the upstream computes for that team, as several result sets. Returns one team's passing dashboard: the pass-type breakdowns the upstream computes for that team, 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_pass"
  }
}

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?

With no annotations, the description carries the full behavioral burden. It does disclose one genuinely useful trait absent from structured data: the response comes back as several result sets. It says nothing about what those sets contain, pagination, or error behavior for invalid team ids.

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 pasted twice verbatim, which is pure waste and suggests an assembly bug. The one unique sentence is front-loaded and clear, but the duplication halves the effective density.

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 five-parameter analytics tool with no output schema and no annotations, the description is thin. It flags that multiple result sets are returned, which is helpful, but never characterizes them, so an agent cannot anticipate the return shape beyond that hint.

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%, with enums spelled out for per_mode, league_id, and season_type, so the schema does the heavy lifting. The description adds no format, default, or interaction detail beyond what the schema already documents.

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 one team's passing dashboard with the pass-type breakdowns. The word "team's" implicitly separates it from player-level siblings such as nba_player_pt_shot, but no sibling is named and the nature of the "pass-type breakdowns" stays hand-wavy.

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 guidance, no prerequisites, and no routing to alternatives such as nba_team_pt_shot or nba_pt_stats, which sound closely related. The agent must infer selection from tool names alone.

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

Deploy Server