PuckAPI

Line movement

get_line_movement

Read-onlyIdempotent

Use when analyzing how betting lines moved over time. Returns time-series snapshots grouped by bookmaker. Most expensive tool (25 cr). If you only need current lines, use get_odds (10 cr) instead. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

Input Schema

Name	Required	Description	Default
`game_id`	Yes	NHL game ID
`bookmaker`	No	Filter by specific bookmaker key (lowercase)

Output Schema

Name	Required	Description	Default
`game_id`	Yes
`movement`	Yes
`away_team`	Yes
`home_team`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026
- addedOutput schema / properties / movement / additionalProperties / items / properties / source
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds genuinely useful behavior beyond them: it discloses that this is the most expensive tool at 25 credits, that results are grouped by bookmaker, and it carries an important compliance constraint about not computing stakes or recommending bets. It stops short of richer details like pagination or result caps, so 4 rather than 5.

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?

Four short sentences, each earning its place: purpose, return shape, cost/alternative routing, and the compliance guardrail. The routing information is front-loaded where an agent will see it before committing to the 25-credit call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only two-parameter tool with full schema coverage and an output schema, this is complete: it covers purpose, cost, alternative routing, and the responsible-gambling constraint. Nothing an agent needs in order to call it correctly is missing.

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%, so both parameters are already documented, including the lowercase bookmaker note. The description's mention of grouping by bookmaker loosely reinforces the filter but adds no syntax or format detail beyond the schema, so the baseline of 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 ('analyzing how betting lines moved over time') and describes the return shape (time-series snapshots grouped by bookmaker). It explicitly names the sibling get_odds and the distinction, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger ('analyzing how betting lines moved over time') and a when-to-use-the-alternative rule ('If you only need current lines, use get_odds (10 cr) instead'), complete with the cost trade-off. Nothing is left to inference about routing.

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

All PuckAPI tools Inspect

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.