Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_player_dash_pt_pass

Read-only

Get NBA player passing dashboard. Returns one player's passing dashboard: the pass-type and pass-target breakdowns the upstream computes (PASS_TYPE, PASS_TO) with the resulting assist and shooting columns.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season in YYYY-YY form, for example 2026-27. Defaults to the current NBA season.
per_modeNoOptional aggregation; defaults to PerGame.
league_idNoOptional league id; only 00 (NBA) is verified.
player_idNoRequired player id from nba-players or nba-team-roster, for example 1628398.
season_typeNoOptional season type; defaults to Regular Season.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish the safety and openness profile. The description contributes what the payload conceptually contains (PASS_TYPE/PASS_TO breakdowns with assist and shooting columns), but since an output schema exists, this is mild added value rather than essential disclosure.

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?

Two concise sentences with the resource front-loaded and the payload described second. The second sentence partially restates the first ('passing dashboard' repeated), which is minor redundancy but not wasteful.

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

Completeness4/5

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

With full schema coverage, an output schema, and annotations covering safety, the description supplies enough for correct invocation. The only missing piece is routing guidance relative to sibling dashboards.

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%, so all five parameters (season, per_mode, league_id, player_id, season_type) already carry their meaning in the schema. The description adds no parameter guidance such as default behavior or the requirement that player_id be resolved from nba-players, so the baseline 3 applies.

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 verb and resource ('Get NBA player passing dashboard') and clarifies the scope as one player's dashboard with pass-type and pass-target breakdowns. The 'player' qualifier implicitly separates it from the sibling nba_team_dash_pt_pass, though that sibling is never named.

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 only implied by the resource name; there is no statement of when to prefer this over nba_team_dash_pt_pass, the shot dashboards, or nba_box_score_player_track. An agent must infer the per-player scope distinction from the title alone.

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

All Crawlora MCP toolsInspect
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.

Resources