Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_box_score

Read-only

Get one NBA game's traditional box score and return both teams' identity, totals and per-player lines. Use the ten-digit game_id from nba_scoreboard and optionally start_period/end_period in 0 to 14 to bound the periods; a live game can legitimately carry partial player lines, and an unknown or malformed game id is an upstream error rather than an empty result.

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

Input Schema

NameRequiredDescriptionDefault
game_idNoTen-digit game id from nba-scoreboard, for example 0022600196.
league_idNoOptional league id; only 00 (NBA) is verified.
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real behavioral detail: a live game may legitimately carry partial player lines, and an unknown or malformed game_id surfaces as an upstream error rather than an empty result. That error-vs-empty distinction is exactly the kind of context annotations cannot express; only return-format/pagination detail is missing, and an output schema exists.

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?

A single dense sentence, front-loaded with purpose then input sourcing then caveats; nothing is redundant. It is slightly packed with semicolon-joined clauses, which costs a bit of scannability but wastes no words.

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?

For a read-only, 4-parameter lookup with full schema coverage and an output schema, the description covers purpose, input source, period bounding and error semantics. The only gap is that it never mentions the sibling stat variants as alternatives, which is minor given the 'traditional' qualifier.

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 every parameter is already documented, including the 0-14 period range and the '0 means through the end/from the start' semantics. The description restates the period bounds and the game_id source but adds no new syntax or constraints, matching the baseline 3 for a schema-driven tool.

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 traditional box score') and enumerates the payload (both teams' identity, totals, per-player lines). The word 'traditional' implicitly separates it from the advanced/defensive/four-factors/misc siblings, so an agent can route without opening schemas.

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 required input comes from ('the ten-digit game_id from nba_scoreboard') and how to bound output with start_period/end_period. It gives clear invocation context but no explicit when-not-to-use or a named alternative stat variant, which keeps it below a 5.

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