Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_player_info

Retrieves an NBA player's league profile, including full name, birth date, school, country, draft details, jersey number, position, height, weight, team, and season experience.

Instructions

NBA player profile. Returns one player's league profile: full name forms, birth date, school and country, draft year and round, jersey number, position, height and weight, team identity and season experience. Take the player id from nba-players or nba-team-roster.

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

Input Schema

NameRequiredDescriptionDefault
league_idNoLeague id; only 00 (NBA) is verified
player_idYesPlayer id from nba-players or nba-team-roster

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/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. 'Returns one player's league profile' discloses cardinality and read-only intent, and the field list reveals what information is exposed. It says nothing about error behavior for an invalid id, permissions, rate limits, or whether league_id values other than 00 are rejected.

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?

Two sentences, front-loaded with the purpose and followed by the field inventory and the id provenance note. The field enumeration is long but each item is informative return-value detail, so virtually every word earns its place.

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?

With no output schema, the description's field inventory is essential and covers the return shape well; input sourcing is also covered. The remaining gaps — error behavior and how this differs from the v2/profile/bio_stats siblings — are minor for a simple single-record lookup.

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 both parameters are already documented — including the enum and the 'from nba-players or nba-team-roster' prose, which the description simply repeats. No additional meaning (id format, valid ranges, what the id represents) is added beyond the schema.

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 league profile) and enumerates the exact fields returned, so an agent knows precisely what comes back. It doesn't explicitly differentiate itself from near-name siblings such as nba_player_profile_v2 or nba_player_bio_stats, which is the only thing keeping it from 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?

It gives one concrete prerequisite — 'Take the player id from nba-players or nba-team-roster' — which is real workflow guidance. However, it never states when to choose this over nba_player_profile_v2 or nba_player_bio_stats, so the alternative-selection decision is left to inference.

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