Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_common_all_players

Retrieve a complete NBA player listing for any season, including team and roster details, to analyze historical or current league-wide player sets.

Instructions

NBA league-wide player listing for a season. Returns the league's complete player listing for a season (the CommonAllPlayers table). Verified columns are PERSON_ID, DISPLAY_FIRST_LAST, ROSTERSTATUS, TEAM_ID, TEAM_NAME, TEAM_ABBREVIATION and PLAYERCODE. This is the widest player listing in the family; use nba-players when you want the index with roster attributes, and this route when you need the historical-to-current player set.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoSeason in YYYY-YY form; defaults to the current NBA season
league_idNoLeague id; only 00 (NBA) is verified
is_only_current_seasonNoWhen true, only players on a current roster are returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose the concrete returned column set (PERSON_ID, ROSTERSTATUS, TEAM_ID, etc.) plus which fields are 'verified', which is valuable given there is no output schema. It stops short of stating whether results are paginated or size-capped, which matters for the self-described 'widest' listing.

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?

Three front-loaded sentences with no filler: purpose and table first, then the return columns, then the sibling routing. The column enumeration is dense but earns its place as the only documentation of the return shape.

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?

For a zero-required-parameter read tool with no output schema and no annotations, the description covers purpose, return shape, and sibling routing. The remaining parameter defaults are handled adequately by the schema descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by framing the default result as a 'historical-to-current player set', which clarifies what is_only_current_season=false actually yields. It also corroborates the league_id restriction to NBA 00.

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

Purpose5/5

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

The description names a specific verb and resource ('league-wide player listing for a season', the CommonAllPlayers table) and explicitly positions itself against the sibling nba-players, calling itself 'the widest player listing in the family'. An agent can distinguish it from nba-players without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: use nba-players for 'the index with roster attributes', and this route for 'the historical-to-current player set'. That names the alternative and the condition that selects it, leaving nothing 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