Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nhl_gamecenter_boxscore

Read-only

Read the NHL gamecenter boxscore for one source game ID and return the upstream object including its game identity, teams and player statistics. game_id is a required 10-digit NHL game ID (get one from nhl_schedule). The upstream object is preserved without derived statistics or local filtering; an invalid ID is rejected and a malformed or incomplete gamecenter body is reported as an upstream failure rather than a partial boxscore.

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": {
      "game_id": "<game_id>"
    },
    "name": "nhl_gamecenter_boxscore"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesRequired 10-digit NHL game ID, for example 2026020262. Get one from the schedule resource (nhl_schedule); the upstream gamecenter object is preserved as returned.

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=true and openWorldHint=true, so the description's added value is behavioral: the upstream object is preserved without derived statistics or local filtering, and failures (invalid ID, malformed body) are surfaced rather than papered over with a partial result. That is meaningful disclosure beyond the annotations, though it says nothing about size, latency, or rate-limit behavior for what can be a large payload.

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 sentences, front-loaded with purpose then parameters then behavior, and nothing is padded. The closing clause is slightly long but each clause carries distinct information about failure modes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the description still characterizes the response shape at a high level. For a one-parameter read tool it covers purpose, ID sourcing, preservation semantics, and error behavior — an agent has everything needed to call it correctly.

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 single game_id property already documents the 10-digit format, the example value, and the nhl_schedule provenance. The description largely restates that ("a required 10-digit NHL game ID (get one from nhl_schedule)") without adding constraints such as how the endpoint behaves for IDs from a different season or format.

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 ("Read the NHL gamecenter boxscore") and scopes it to "one source game ID," immediately separating it from the multi-game siblings like nhl_schedule. It also enumerates what the returned object contains (game identity, teams, player statistics), so an agent knows exactly what it is asking for.

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 clear context for invocation by naming nhl_schedule as the source of a valid game_id, which removes the main prerequisite ambiguity. It does not explicitly contrast itself with the identical-domain sibling nhl_gamecenter_play_by_play, so there is no stated when-not-to-use case.

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