Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_players

Read-only

Get 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
activeNoOptional flag; when true only players active in the season are returned.
seasonNoOptional season in YYYY-YY form, for example 2026-27. Defaults to the current NBA season.
team_idNoOptional team id from nba-standings or nba-teams; narrows the index to that team's players.
league_idNoOptional league id; only 00 (NBA) is verified.

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 and openWorldHint, so the description's job is to add context – and it does, describing the returned rows (player id, first/last name, team id, roster attributes) and the pivoting role of the ids. It stops short of volume or truncation behavior for a league-wide index, which is the remaining unknown.

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?

Front-loaded with the purpose and free of boilerplate, but the second sentence largely restates the first ("every player id for a season" vs "returns the league's player index for a season") before adding the row fields. Tightening that overlap would make it fully economical.

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 annotations, full schema coverage and an output schema, the description covers everything an agent needs to pick and invoke this tool, including why the ids matter downstream. The only gap is a hint about scale or whether a full-season index is paginated or capped.

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 the baseline of 3 applies: season format, active flag, team_id source and league_id verification are all documented in the schema already. The description only restates team_id narrowing, adding no syntax or semantics 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?

States a specific verb and resource ("Get NBA player index") plus the scope ("every player id for a season") and the row shape. It also positions the tool against a generic alternative (guessing an id) and names the consumers of the returned ids, so an agent can recognize it without opening the 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?

Gives an explicit routing rule: "call this instead of guessing an id" because nba-player-info, nba-box-score and nba-play-by-play accept these ids. It also tells the agent to pass team_id to narrow to one roster, which is actionable selection guidance rather than implied usage.

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