Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_players

Discover every NBA player ID for a season so you can query player info, box scores, and play-by-play without guessing IDs; filter by team or active status.

Instructions

NBA player index: every player id for a season. Returns the league's player index for a season, one row per player with player id, first and last name, team id and the source's roster attributes. This is the family's player-id discovery route: the ids it returns are what nba-player-info, nba-box-score and nba-play-by-play accept, so call this instead of guessing an id. Pass team_id to narrow the index to one roster.

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

Input Schema

NameRequiredDescriptionDefault
activeNoWhen true, keep only players active in the season
seasonNoSeason in YYYY-YY form; defaults to the current NBA season
team_idNoOptional team id from nba-standings; narrows the index to that roster example(1610612741)
league_idNoLeague id; only 00 (NBA) is verified

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the result shape (one row per player, with the listed fields) and the interoperability of the returned ids. It stops short of stating that this is a pure read with no side effects, and says nothing about pagination, row counts, or error behavior for an unknown team_id or season.

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 definition is front-loaded with the identity of the tool and stays to four tight sentences with no filler. There is mild redundancy between sentence one and sentence two, both of which describe the same seasonal index of player ids.

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?

Because there is no output schema and no annotations, the description must cover return values and safety itself; it does describe the per-player record and the read-style discovery role, which is enough for an agent to call it. It leaves open pagination limits and what happens with an invalid season or team_id, the only substantive gaps for a four-parameter list tool.

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 four parameters are already documented, and the description's team_id remark (narrow to one roster) is largely duplicative of the schema text. It adds no format or edge-case detail for season, league_id, or active, so it meets but does not exceed the baseline for a fully documented 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?

"NBA player index: every player id for a season" states a specific noun-and-scope, and the second sentence enumerates the returned fields (player id, names, team id, roster attributes). The definition also positions it against the rest of the family by naming the tools that consume its ids (nba-player-info, nba-box-score, nba-play-by-play), so an agent can place it without opening a 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?

The description explicitly frames the tool as "the family's player-id discovery route" and tells the agent to "call this instead of guessing an id", which is a concrete when-to-use rule plus the failure mode it prevents. It also gives a narrowing condition ("Pass team_id to narrow the index to one roster") that explains the main optional parameter's purpose rather than restating it.

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