Skip to main content
Glama

Stratalize Intelligence

Get Sports Nhl Scores

get_sports_nhl_scores
Read-only

Live NHL game scores, game status, and results for the past 7 days and next 7 days. Returns teams, scores, and game status. Source: TheSportsDB. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds genuinely new context: the upstream source (TheSportsDB), a per-call price of $0.02 USDC, and an attestation/verification path. The 'post-quantum signed settlement receipt' phrasing is somewhat promotional, but it does convey provenance and a cost dimension an agent should know before calling.

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?

Three sentences, front-loaded with purpose and window, then return fields, then provenance/cost. No sentence is redundant relative to what an agent needs, and the marketing-adjacent attestation line still carries the payment and verification facts.

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 zero-parameter read with annotations covering safety, the description supplies scope, return fields, source, and cost, which is sufficient to invoke it correctly. It stops short of describing the shape of each game record, and since no output schema exists that detail is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline of 4 applies since the fixed 7-day window is stated and no parameter semantics are needed.

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?

The description names a specific verb and resource ('Live NHL game scores, game status, and results') plus an explicit scope ('past 7 days and next 7 days'), so an agent can separate it from get_sports_nba_scores, get_sports_mlb_scores, and the multi-league tool on the strength of the text alone.

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 7-day window and single-league scope imply appropriate use, but the description never states when to prefer a sibling such as get_sports_scores_multi for multi-league queries, nor any exclusions. Usage is inferable but not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources