Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nba_player_clutch

Retrieve NBA clutch player statistics by season, clutch window, and score margin, including shooting and counting stats for analyzing late-game performance.

Instructions

Returns the league's clutch player table for one clutch window and score margin: the players' clutch shooting and counting stats. Returns the league's clutch player table for one clutch window and score margin: the players' clutch shooting and counting stats.

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

Input Schema

Name	Required	Description
`season`	No	Optional season in YYYY-YY form; defaults to the current NBA season.
`per_mode`	No	Optional aggregation.
`league_id`	No	Optional league id; only 00 (NBA) is verified.
`point_diff`	No	Optional point margin; only 5 is verified.
`clutch_time`	No	Optional clutch window; only 'Last 5 Minutes' is verified.
`season_type`	No	Optional season type.
`ahead_behind`	No	Optional score-margin filter; only 'Ahead or Behind' is verified.
`measure_type`	No	Optional statistic family.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing beyond the fact that a table is returned. It does not say what happens when optional parameters are omitted (the schema says they default, but the description does not confirm the returned slice), whether the result is a single row set or paginated, or what the response contains structurally.

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 — a clear structural defect. What remains is short and front-loaded, but the duplication signals careless authoring and wastes the reader's attention.

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

Completeness2/5

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

For an eight-parameter tool with no annotations and no output schema, the description is thin: it omits the restricted/verified enum values, default resolution behavior, and any hint of the return shape. An agent could call it, but only by reading the schema closely and guessing at what comes back.

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 seven enums, so the schema already explains every parameter, and the description adds only the framing that the clutch window and score margin jointly define one slice of the table. That framing is mildly useful but adds no syntax, default behavior, or interaction detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ("Returns the league's clutch player table") plus the two scoping dimensions (clutch window and score margin), which is more specific than a bare name. However, it never distinguishes this tool from stat-oriented siblings such as nba_player_stats or nba_player_career_stats, so an agent cannot tell from the text alone why it would pick this over a general player-stats tool.

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 statement of prerequisites, and no named alternative. Critically, the schema only permits a single verified value for clutch_time ("Last 5 Minutes"), point_diff (5), ahead_behind, and league_id, but the description says nothing about this, so an agent may assume it can request arbitrary clutch windows or margins.

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

Deploy Server