Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_team_roster

Read-only

Get NBA team roster for a season. Returns one team's roster for a season, one row per player with player id, name, nickname, player slug, jersey number, position, height and weight. Player ids from this route are the input nba-player-info accepts; take the team id from nba-standings.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season in YYYY-YY form, for example 2026-27. Defaults to the current NBA season.
team_idNoRequired team id from nba-standings, for example 1610612741.
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

A3.9/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 safety profile is covered. The description adds real behavioral value beyond that: it discloses the result shape (one row per player) and identifies itself as the authoritative source of player ids consumed downstream. It does not mention pagination, missing-team behavior, or whether leagues other than 00 return empty data.

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 tight sentences, front-loaded with the action and followed by return shape then integration hints. Minor waste in the near-repetition of "for a season" in the first two sentences.

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?

Output schema exists and annotations cover the safety profile, so the description only needed to establish purpose and the data-flow relationship, which it does. Remaining gaps (behavior for unverified league_id values, empty rosters) are small for a single-team read 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 description coverage is 100%, so all three parameters are already documented, including the YYYY-YY format and the team_id example. The description echoes the same provenance notes (team_id from nba-standings) rather than adding syntax, defaults, or constraints. Baseline 3 applies because the schema does the heavy lifting.

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 definition opens with a specific verb and resource ("Get NBA team roster for a season") and narrows scope to one team and one season, plus it enumerates the returned per-player fields. It never distinguishes itself from the other roster siblings in the catalog (espn_team_roster, yahoo_sports_team_roster, mlb_team_roster), so an agent must infer the NBA-only boundary from the tool name.

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

Usage Guidelines4/5

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

It gives concrete workflow guidance: take team_id from nba-standings and feed the returned player ids into nba-player-info. That is unusually actionable lineage for this catalog. It stops short of naming when to prefer a different roster source or nba_common_all_players instead, so no explicit exclusions.

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