Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nhl_standings

Read-only

Read the NHL standings snapshot for one date or for the current snapshot and return the upstream standings object: its standingsDate plus the native standings rows with team IDs, names/abbreviations and the source's points/games-played and ranking fields. date is an optional ISO YYYY-MM-DD value; omitting it requests the upstream now resource. The upstream structure is preserved without derived stats or local sorting, and malformed or incomplete bodies are rejected instead of being presented as a snapshot.

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

Input Schema

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

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

Beyond the readOnlyHint/openWorldHint annotations it discloses meaningful behavioral traits: upstream structure is preserved verbatim, no derived stats or local sorting are applied, and malformed or incomplete bodies are rejected rather than returned as a snapshot. It stops short of describing error surface or caching/rate behavior, so not a 5.

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?

A single front-loaded sentence that opens with the verb and resource, then layers scope, parameter meaning, and fidelity guarantees. It is dense but every clause carries information; only mild tightening would be possible.

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?

An output schema exists, so return values need not be spelled out, yet the description still sketches the standingsDate plus rows shape. Combined with the date semantics and the rejection of malformed payloads, an agent has what it needs; only the treatment of upstream failures is left unstated.

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 date parameter is already fully documented in the schema, including format and pass-through behavior. The description restates that omission yields the now snapshot and that values are passed through, adding little beyond the structured field, so the 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 ("Read the NHL standings snapshot") plus the two access modes, one date or the current snapshot. The NHL scoping distinguishes it from the many other league standings siblings, and it cites what the returned object contains.

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?

Explains the choice between supplying a date and omitting it ("omitting it requests the upstream now resource"), which is useful invocation guidance. It never names an alternative tool or states when another standings source should be preferred, so the when-to-use-vs-alternatives dimension is only implied.

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