Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nhl_standings

Fetch NHL standings for a given ISO date or use current data by omitting the date, preserving team IDs, standings fields, and source dates.

Instructions

Get NHL standings. Returns the NHL standings resource for the requested ISO date. Omitting date uses the upstream now resource. The response preserves NHL team IDs, standings fields, and source dates.

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
dateNoISO date (YYYY-MM-DD); defaults to now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose that omitting the date falls back to the upstream `now` resource and that the response preserves team IDs, standings fields, and source dates, which is useful read-only context. It does not address permissions, rate limits, pagination, or any error behavior for malformed dates.

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 verb+resource and free of filler. The opening 'Get NHL standings.' slightly restates the second sentence, but the overall length is appropriate for a one-parameter tool.

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 read tool with one optional parameter, no output schema, and no nesting, the definition covers purpose, default behavior, and the general shape of the response. Remaining gaps (exact standings fields returned) are acceptable for this level of complexity.

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 documented as an ISO date defaulting to now, so the baseline is 3. The description adds only the mild clarification that the default comes from an upstream `now` resource, without format edge cases or timezone 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?

States a specific verb and resource ('Get NHL standings') and names the returned resource explicitly. The league qualifier implicitly separates it from the many other *_standings siblings, but it never names one of them (e.g. espn_standings) to disambiguate the choice.

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?

Usage is only implied: an agent can infer 'call this when you need NHL standings,' and the note about omitting the date gives a default-behavior hint. There is no explicit when-to-use framing, no exclusions, and no pointer to an alternative standings source.

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