Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_player_clutch

Read-only

Get 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

NameRequiredDescriptionDefault
seasonNoOptional season in YYYY-YY form; defaults to the current NBA season.
per_modeNoOptional aggregation; defaults to PerGame.
league_idNoOptional league id; only 00 (NBA) is verified.
point_diffNoOptional point margin; only 5 is verified.
clutch_timeNoOptional clutch window; only 'Last 5 Minutes' is verified.
season_typeNoOptional season type.
ahead_behindNoOptional score-margin filter; only 'Ahead or Behind' is verified.
measure_typeNoOptional statistic family; defaults to Base.

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds nothing further: no note about which parameter combinations are actually verified, no defaults surfaced (even though the schema does declare defaults), no indication of result size or pagination. It simply restates the same sentence twice.

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

Conciseness3/5

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

The single sentence is repeated verbatim, wasting roughly half the text with zero informational gain, and it opens with the awkward fragment 'Get Returns'. The remaining content is short and front-loaded, which keeps the damage limited.

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?

An output schema exists, so return values need not be explained, and the schema fully documents all eight optional parameters with defaults. What is missing is behavioral context appropriate to an open-world read: which parameter values are verified, and how this league table differs from the clutch dashboard siblings.

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 eight parameters including season, per_mode, point_diff and clutch_time are already documented. The description only echoes the clutch-window and score-margin dimensions and adds no meaning beyond the schema, so the baseline of 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 resource (the league's clutch player table) and scopes it to one clutch window and score margin, with clutch shooting and counting stats called out. The phrasing 'Get Returns the league's...' is garbled, and it never distinguishes this league-wide table from siblings like nba_player_dash_by_clutch or nba_team_dash_by_clutch, but the resource itself is unambiguous.

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 when to prefer a sibling clutch tool, and no prerequisites or caveats. The agent must infer that this is the league-wide clutch leaderboard rather than a per-player dashboard.

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