Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_common_all_players

Read-only

Get 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
seasonNoOptional season in YYYY-YY form, for example 2026-27. Defaults to the current NBA season.
league_idNoOptional league id; only 00 (NBA) is verified.
is_only_current_seasonNoOptional flag; when true only players on a current roster are returned. Defaults to false, which includes historical rows.

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's job is to add operational context, which it does: it discloses the underlying table, the verified column set, and that is_only_current_season defaults to false so historical rows are included. It stops short of covering rate limits, pagination, or response shape (the latter mitigated by the output schema).

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 sentences, front-loaded and free of filler, with the routing guidance placed last where it is most useful for disambiguation. Minor redundancy: the second sentence largely restates the first before adding the table name and column list.

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?

For a read-only, three-optional-parameter listing tool with an output schema and full schema coverage, the description covers scope, defaults, verified values, and the sibling alternative. Remaining gaps (pagination, ordering, response size) are modest given the output schema is available.

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 the parameter descriptions already carry season format, league_id constraints, and the is_only_current_season default; baseline is 3. The description's mention of the "historical-to-current player set" and "only 00 (NBA) is verified" reinforces those semantics but does not add new parameter-level detail beyond the schema.

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 opens with a specific verb and resource ("Get NBA league-wide player listing for a season") and names the backing table (CommonAllPlayers) plus the exact verified columns, so an agent knows precisely what data comes back. It also explicitly distinguishes itself from the sibling nba-players, calling this "the widest player listing in the family."

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 names the alternative (nba-players) and the condition that selects each route: nba-players for "the index with roster attributes," this tool for "the historical-to-current player set." That is explicit when-to-use/when-to-use-the-other guidance rather than implied context.

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