Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nhl_schedule

Retrieve the NHL schedule for a specified ISO date or the current schedule when no date is given, preserving game IDs, game states, and source structure.

Instructions

Get NHL schedule. Returns the NHL schedule resource for the requested ISO date. Omitting date uses the upstream now resource. The response preserves game IDs, game state, and source schedule structure.

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": "nhl_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO date (YYYY-MM-DD); defaults to now

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?

With no annotations, the description carries the full burden. It does disclose the default-resolution behavior (falling back to an upstream `now` resource) and that the response preserves game IDs, game state, and source structure, which is meaningful context. It says nothing about pagination, rate limits, or whether one date yields a full slate of games vs a single entry.

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 short sentences, front-loaded with the core purpose, then default behavior, then response guarantees. Nothing is padded, though the final sentence about preserving structure is slightly abstract.

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

Completeness3/5

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

For a single optional parameter, no output schema, and no annotations, the description covers purpose, default behavior, and rough response contents. It remains vague about what exactly a schedule resource contains (one game vs all games on the date), which an agent calling it may want to know.

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 schema already documents the `date` parameter format and its default to now. The description restates the default and adds the phrase 'upstream `now` resource', a marginal clarification beyond the schema but no new format or edge-case semantics.

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 uses a specific verb and resource ('Get NHL schedule') and clarifies the return is the schedule resource for a requested ISO date. It implicitly distinguishes itself from the gamecenter boxscore/play-by-play siblings by scoping to schedule, though it never names or contrasts them explicitly.

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

Usage Guidelines3/5

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

It gives one concrete usage rule — omit the date to get the upstream `now` resource — which is genuinely useful. However, there is no guidance on when to prefer this over nhl_seasons, nhl_standings, or the gamecenter tools, and no stated exclusions or prerequisites.

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