Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_team_roster

Retrieve an NBA team roster for a specified season, returning each player's ID, name, jersey number, position, height, and weight for lineup and player-info lookups.

Instructions

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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>"
    },
    "name": "nba_team_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoSeason in YYYY-YY form; defaults to the current NBA season
team_idYesTeam id from nba-standings
league_idNoLeague id; only 00 (NBA) is verified

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the return shape (one row per player plus the exact columns) and the cross-tool contract for identifiers. It does not discuss error behavior for an invalid season or team id, or any rate/coverage limits, but for a read-only lookup the safety profile is adequately implied by "Returns".

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose first, output shape second, identifier provenance last. Nothing is redundant and the ordering matches what an agent needs to decide and then invoke.

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?

Since there is no output schema, the description correctly compensates by enumerating returned columns, and it covers input provenance. For a simple three-parameter read tool this is nearly complete; only failure/edge behavior is unaddressed.

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% and the schema already states that team_id comes from nba-standings and that season defaults to the current NBA season, so the description largely repeats structured information. It adds no new syntax or format guidance for season or league_id beyond what is documented.

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?

"Returns one team's roster for a season, one row per player" gives a specific verb, resource, scope and result granularity. It also enumerates the returned fields (player id, name, nickname, slug, jersey number, position, height, weight), so an agent knows exactly what it gets without inspecting 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 Guidelines4/5

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

It gives concrete workflow routing: take the team id from nba-standings, and the player ids produced here are the input nba-player-info accepts. That is clear context for when this tool belongs in a chain, though there is no explicit statement of when not to use it or of alternatives within the roster family.

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