Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nhl_schedule

Read-only

Read the NHL schedule snapshot for one date or for the current schedule and return the upstream schedule object: nextStartDate, previousStartDate and the native gameWeek entries with their date and source game IDs, state and schedule structure. date is an optional ISO YYYY-MM-DD value; omitting it requests the upstream now resource. The upstream shape is preserved with no local filtering or derived fields, and malformed or incomplete bodies are rejected rather than returned as an empty schedule.

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
dateNoOptional ISO date (YYYY-MM-DD), for example 2026-11-06. Omit it to read the upstream now schedule; any supplied value must be a real date and is passed through to the date-specific schedule resource.

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description still adds meaningful behavior: no local filtering or derived fields, upstream shape preserved verbatim, and malformed or incomplete bodies rejected rather than silently returned as an empty schedule. That last point is a genuinely useful failure-mode disclosure rarely found in structured fields.

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?

Front-loaded with the action and scope, then behavior, then the parameter note. It is a single dense paragraph that could be split, and the enumeration of upstream field names is slightly heavy, but every sentence carries information.

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?

With an output schema present the description needn't detail return values, yet it flags the pass-through nature and the rejection-on-malformed behavior, which the schema cannot express. For a one-optional-parameter read tool this is close to fully sufficient; only sibling routing is thin.

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 ISO format, an example, and the omit-to-get-now behavior. The description restates the same semantics rather than adding new meaning such as validation rules or timezone handling, so the baseline applies.

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?

Names a specific verb and resource ("Read the NHL schedule snapshot") and scopes it to one date or the current schedule, then enumerates the returned upstream fields (nextStartDate, previousStartDate, gameWeek entries). An agent can distinguish it from other-sport schedule tools by name alone, though no NHL-specific sibling (e.g. nhl_seasons, nhl_standings) is explicitly excluded.

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?

The definition covers the two calling modes — supply a date for a specific day, omit it for the upstream now resource — which is real usage context. It gives no explicit when-not guidance or routing to alternative NHL endpoints for related data, so usage is implied rather than fully directed.

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