Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nhl_gamecenter_boxscore

Retrieve the NHL gamecenter boxscore for a given 10-digit game ID, preserving the source team and player statistics.

Instructions

Get NHL game boxscore. Returns the upstream gamecenter boxscore for one NHL game ID, preserving the source's team and player statistics.

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_idYes10-digit NHL game ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It usefully states that results are an upstream gamecenter passthrough preserving source team and player statistics, which signals that the data is not normalized. It does not explicitly discuss read-only safety, error behavior for invalid IDs, or rate limits.

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?

The description is two sentences, front-loaded with the purpose and followed by a useful note about the upstream-preservation behavior. There is no filler or unnecessary repetition.

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 simple one-parameter read tool with no output schema, the description covers what it returns and the upstream-preservation caveat. It stops short of documenting failure cases or return structure, but the core invocation context is complete.

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 parameter is fully documented as a 10-digit NHL game ID. The description only restates that one game ID is required and adds little semantic detail beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Get') and resource ('NHL game boxscore') and constrains the scope to one game ID, so the agent knows exactly what it retrieves. It does not explicitly differentiate this from nearby siblings like nhl_gamecenter_play_by_play, though 'boxscore' versus play-by-play is reasonably self-evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as nhl_gamecenter_play_by_play or nhl_schedule. The only implied condition is that the caller has a valid NHL game ID.

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