Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_player_career_stats

Read-only

Get NBA player season-by-season and career statistics. Returns one player's career statistics as several tables: the season-by-season regular-season line, the career regular-season totals, the season-by-season postseason line and the career postseason totals. Verified columns are SEASON_ID, TEAM_ID, GP, GS, MIN and PTS. per_mode PerGame or Totals is validated against the values verified on this endpoint.

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

Input Schema

NameRequiredDescriptionDefault
per_modeNoOptional aggregation; PerGame or Totals. 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.

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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes further by disclosing the exact return shape (four tables: season regular season, career regular-season totals, season postseason, career postseason totals) and stating which columns are verified (SEASON_ID, TEAM_ID, GP, GS, MIN, PTS). It also flags the validation boundary for per_mode, which tells the agent the underlying data source is partially unverified — real context beyond annotations.

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?

It is front-loaded with purpose, then return shape, then verified-column and validation caveats — a sensible ordering with no filler sentences. The enumerated column list is slightly dense but each item carries information about data reliability.

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

Completeness5/5

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

With annotations covering safety, a full output schema covering return structure, and 100% schema description coverage, the description only needs to supply the caveats — which it does via the verified-column list and the per_mode validation note. Nothing an agent needs in order to call this correctly appears missing.

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 coverage is 100%, so all three parameters are already documented in structured fields, which sets the baseline at 3. The description adds only the note that per_mode values are validated against verified endpoint values, and does not explain player_id sourcing or league_id constraints beyond what the schema states.

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 opens with a specific verb and resource ('Get NBA player season-by-season and career statistics') and enumerates the exact outputs, so an agent can distinguish it from per-game-log or single-season siblings. It never names an alternative tool, but the scope is clear enough without that.

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: the season/career framing implies 'use me when you want career aggregates,' and the phrase 'player id from nba-players or nba-team-roster' gives a sourcing hint for the required id. There is no explicit when-not-to-use or comparison to nba_player_stats or nba_player_game_logs.

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