Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_pt_stats

Read-only

Get 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

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.
season_typeNoOptional season type; defaults to Regular Season.
pt_measure_typeNoOptional tracking measure; only SpeedDistance is verified. Defaults to SpeedDistance.

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 description goes beyond the readOnlyHint/openWorldHint annotations by disclosing a real failure mode: a trimmed query returns HTTP 500, so the full dashboard scope is always sent, and pt_measure_type is pinned. That is genuinely useful behavioral detail, though return shape and any rate/limit behavior are left unstated (the output schema covers the former).

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 tight sentences, front-loaded with what the tool returns, then the operational constraint. No padding. A small deduction because the second and third sentences partially repeat the same pinning idea.

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?

For a read-only, single-purpose dashboard tool with a fully documented schema and an output schema, this is close to complete: the quirky 500-on-trimmed-query caveat is exactly the kind of thing an agent needs and rarely gets. Only the missing sibling differentiation keeps it from a 5.

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 are already documented with defaults. The description only reinforces the pt_measure_type pinning, which the schema itself already states as 'only SpeedDistance is verified.' Baseline 3 is appropriate.

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?

Clear verb and resource: returns the league-wide NBA player-tracking dashboard for a single tracking measure. The pinned measure (SpeedDistance) sharpens scope. It does not explicitly contrast with the many sibling tracking tools (nba_hustle_stats, nba_player_dash_pt_pass, etc.), so a 4 rather than a 5.

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?

The description implies usage (fetch the league dashboard for one measure) and warns that only SpeedDistance is verified, but it never states when to choose this over sibling tracking tools or what disqualifies a caller. Three is the minimum viable here.

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