Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

nhl: Get scores

nhl_get_scores
Read-onlyIdempotent

Retrieve live and final scores for today's NHL games to check current results or completed matchups. Optionally limit returned fields for focused score data.

Instructions

Get live and final scores for today's NHL games.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds that results include live (in-progress) and final states, which is useful context, but says nothing about refresh cadence, rate limits, or behavior when no games are scheduled.

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?

One sentence, front-loaded with the verb and resource, with the scope constraint appended. No filler or redundant restatement of the name.

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?

Adequate for a simple no-required-param scoreboard read whose annotations cover safety and which has no output schema. Still, it omits what the timezone/'today' boundary means and whether live games include partial scores, leaving minor gaps.

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?

The single optional 'fields' parameter is fully documented in the schema (100% coverage), so the schema does the heavy lifting. The description adds no meaning about what field keys are valid or how filtering behaves, matching the baseline 3 for high-coverage schemas.

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 (Get) and resource (scores) with scope qualifiers: NHL, today's games, live and final. This separates it well from nhl_get_schedule and nhl_get_game_boxscore, though it does not name a sibling 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?

'Today's games' and 'live and final' imply when the tool is useful (a same-day scoreboard lookup), but there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives like nhl_get_schedule or nhl_get_standings.

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