Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_play_by_play

Read-only

Get one NBA game's play-by-play and return every action with period, clock, team, player, score and description fields. Use the ten-digit game_id from nba_scoreboard and optionally start_period/end_period to bound the scan; video availability is reported as a source flag, and an unknown game id is an upstream error. This is the most terms-exposed NBA surface, so keep the call scoped to one game.

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

Input Schema

NameRequiredDescriptionDefault
game_idNoTen-digit game id from nba-scoreboard, for example 0022600196.
end_periodNoOptional last period to include, 0 to 14; 0 means through the end.
start_periodNoOptional first period to include, 0 to 14; 0 means from the start.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds behavior beyond them: the result includes a video-availability source flag, an unknown game id surfaces as an upstream error, and the endpoint is described as the most terms-exposed NBA surface, which implies rate/scope pressure. What it omits is whether the full play-by-play is paginated or truncated for long games.

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 sentences, each carrying distinct information: what is returned, how to call it, and the operational constraint. The purpose is front-loaded and no sentence is redundant.

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 an output schema present and full parameter coverage, the description covers the remaining agent-facing concerns: identifier provenance, period scoping, error behavior on a bad id, and a cost/terms warning. Only pagination or result-size behavior for very long games is left 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%, so all three parameters are already documented in structured form, including the 0-14 range and the '0 means from the start / through the end' semantics. The description adds only the intent behind the period bounds ('to bound the scan') and reinforces the ten-digit game_id format, which is marginal 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 one NBA game's play-by-play') and enumerates the returned fields (period, clock, team, player, score, description). It also anchors itself to the sibling that supplies its key input ('the ten-digit game_id from nba_scoreboard'), so an agent can tell it apart from scoreboard and from other sports' play-by-play tools 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 Guidelines4/5

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

It states where the identifier comes from (nba_scoreboard), how to narrow the scan (start_period/end_period), and a hard usage constraint ('keep the call scoped to one game'). It does not name an explicit when-not or an alternative NBA play-by-play source, but no such sibling is evident, so the guidance is effectively complete for selection.

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