Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_game_detail

Read-only

Get NBA game summary detail from nba.com. Returns one game's summary detail from nba.com's game page, read from the page's embedded JSON state: status and clock, game duration, attendance and sellout flag, venue id, name, city, state, country and timezone, the officiating crew with names and jersey numbers, series text, and each team's per-period scoring with a derived game total. Use nba-box-score for per-player statistics; this route is the game-level summary the box score does not carry.

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

Input Schema

NameRequiredDescriptionDefault
game_idNoTen-digit game id from nba-scoreboard, for example 0022600196.

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
Behavior3/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 known. The description usefully adds the data provenance ('read from the page's embedded JSON state' via nba.com), which signals a scraped, live-source route rather than a cached API. It says nothing about rate limits, failure modes when a game has no box score yet, or staleness — beyond that, a 3 is warranted.

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?

Purpose and the sibling distinction are front-loaded, and both sentences carry routing value. The long mid-sentence enumeration of returned fields (venue address components, officiating crew jersey numbers, per-period scoring) is somewhat redundant given an output schema exists and pads the description.

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 single-parameter read tool with full schema coverage, an output schema, and safety annotations, the definition gives an agent enough to call it correctly. Its only shortfall is not clarifying edge behavior (e.g. incomplete games, missing officials), which is arguably outside scope given the output schema.

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 game_id is documented with a ten-digit example sourced from nba-scoreboard, so semantics are already carried by the schema. The description only implies single-game scoping ('one game's summary detail') and adds no format or validity detail beyond it. Baseline 3 applies.

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 game summary detail from nba.com') and immediately scopes it as a single-game, game-level summary. It also names the sibling it is not (nba-box-score) and the exact distinction, so an agent can route without opening either 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?

Explicitly routes per-player statistics to nba-box-score and claims the game-level summary that tool lacks, which is a clear when-to-use signal. It does not address other plausible alternatives (e.g. scoreboard or league game logs) or prerequisites such as obtaining a valid game_id first, but the schema covers the id source.

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