Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_player_profile_v2

Retrieve a player's full stat profile: season-by-season regular-season lines, career regular-season totals, and postseason equivalents. Compare regular-season and playoff performance in one request.

Instructions

Returns one player's full profile stat set: the season-by-season regular-season line, the career regular-season totals and the postseason equivalents. Returns one player's full profile stat set: the season-by-season regular-season line, the career regular-season totals and the postseason equivalents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "player_id": "<player_id>"
    },
    "name": "nba_player_profile_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
per_modeNoOptional aggregation.
player_idYesRequired player id from nba-players or nba-team-roster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the shape of what comes back (three stat groupings) — useful since there is no output schema. However, it says nothing about behavior for an invalid or unknown player_id, whether missing seasons are omitted or null, response size, or latency, so an agent cannot predict edge-case behavior.

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?

The content itself is front-loaded and only two clauses long, but the entire description is repeated verbatim twice, which is pure waste and reads as a data-generation defect.

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?

The description covers the return payload, which is the main gap given no output schema, and the schema fully documents the two inputs. What's missing for a profile tool with 30+ stat siblings is any disambiguation or behavioral detail about ID validation, leaving an agent able to invoke it but not confident it picked the right one.

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 both parameters are already documented, including the enum values for per_mode and the sourcing of player_id. The description adds no meaning beyond the schema — it never mentions per_mode or explains how aggregation changes the returned line — 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 (one player's full profile stat set) and enumerates what's inside it: season-by-season regular-season line, career regular-season totals, and postseason equivalents. That content breakdown distinguishes it somewhat from generic stat siblings, but it never explains how it differs from nba_player_stats, nba_player_career_stats, or nba_player_bio_stats, and the unexplained 'v2' suffix leaves versioning ambiguous.

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 at all: no statement of the conditions that favor this tool over the many nba_player_* siblings, and no exclusions. The only routing hint available is the schema's note that player_id comes from nba-players or nba-team-roster, which addresses ID sourcing rather than tool selection.

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

Deploy Server

Other Tools