Skip to main content
Glama

NHL line movement

invoke_nhl_line_movement
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. NHL line movement, tracked by BankrollSZN: for each upcoming game the opening and current moneylines, puck line, total and team implied goals, the change since open and the biggest move first. include_series true adds every captured price with its time (UTC). Use it to see where the market moved before you build or bet. Refreshes every 15 minutes from the BankrollSZN line movement board.

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation, home or away.
limitNoMaximum rows to return. The plan limit applies on top.
offsetNoPaid plans: next page offset from page.next_offset.
sort_byNoDefault move (biggest change first).
include_seriesNoAdd the full price history per game. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new facts: a 15-minute refresh cadence from the BankrollSZN board, a first-call approval prompt, and default ordering by biggest move. The approval note is useful operational context that no structured field conveys.

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?

Sentences are dense but each carries information, and the field enumeration is efficient. The opening approval-prompt sentence is placed ahead of the actual purpose statement, which buries the lede an agent needs first.

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 no output schema, the description compensates by describing the returned fields, ordering, and refresh cadence. What remains unstated is pagination behavior and the plan-limit interaction, though the limit/offset parameter descriptions partly fill that gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: include_series true returns every captured price stamped in UTC, and sort defaults to biggest change first. The offset/limit parameters are left to the schema, which is acceptable given full coverage.

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?

The description names a specific resource and enumerates exactly what is returned per game: opening and current moneylines, puck line, total, team implied goals, and the change since open. It does not explicitly distinguish itself from close siblings like invoke_nhl_lines or invoke_nhl_line_matchups, so an agent must infer the boundary from the field list alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it to see where the market moved before you build or bet" gives a clear trigger context for selecting this tool. It stops short of naming alternatives or stating when-not-to-use it, so the guidance is directional rather than exhaustive.

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