PuckAPI

This connector has been deprecated

Moved to a server instead of a connector

Prop movement

get_prop_movement

Read-onlyIdempotent

Use to see how one player's prop line moved before a game: every capture we hold, book by book and oldest first, with the line, both prices and the minutes before the start. line_change is the last capture's line minus the first's. The number of captures varies by game and book. Costs 10 credits. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game_id": "<game_id>",
      "player_id": "<player_id>",
      "market": "<market>"
    },
    "name": "get_prop_movement"
  }
}

Input Schema

Name	Required	Description
`market`	Yes	The market: player_points (points), player_goals (goals), player_assists (assists), player_shots_on_goal (shots on goal), player_blocked_shots (blocked shots), player_total_saves (goalie saves), player_goal_scorer_anytime (anytime goal scorer (over = scores)), player_power_play_points (power-play points), player_goal_scorer_first (first goal scorer (over = scores the game's first goal))
`game_id`	Yes	Game id.
`bookmaker`	No	One book's captures, e.g. draftkings.
`player_id`	Yes	Player id (e.g. 8478402) from search_players.

Output Schema

Name	Required	Description	Default
`note`	No
`tool`	No
`books`	Yes
`count`	Yes
`market`	Yes
`credits`	No
`game_id`	Yes
`player_id`	Yes
`player_name`	Yes
`estimate_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description is free to add the non-obvious traits: a fixed 10-credit cost, variability in the number of captures per game and book, deterministic oldest-first ordering, and the definition of the computed line_change field. It also states a hard usage prohibition (no stake/payout/profit math, no bet recommendations, no sportsbook referrals), which is behavioral guidance an agent cannot get from any structured field.

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?

Purpose and output shape are front-loaded in one dense sentence before the cost and compliance notes, so the reader gets the important part first. The line_change definition and the prices disclaimer each earn their place, though the result-shape clause is slightly packed and could be split for readability.

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?

An output schema exists, so return values need not be detailed, yet the description still supplies the ordering, the derived-field formula and the variance in capture count — exactly the context a caller needs to interpret results. Cost, plus a clear boundary on what the data may be used for, rounds out a complete picture for a read-only, single-purpose lookup.

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 description coverage is 100% and the market enum is fully self-documenting, so the schema carries parameter meaning. The description adds only indirect cues — 'book by book' hints that bookmaker narrows to a single book's captures, and 'the number of captures varies by game and book' warns that results may be sparse. It does not say what omitting bookmaker does, so it stays at the baseline.

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 gives a specific verb and resource: see how one player's prop line moved before a game, plus the shape of the result (every capture, book by book, oldest first, line/prices/minutes-to-start). That is far more precise than a tautology and implicitly separates it from game-level line movement. It never names a sibling such as get_line_movement, get_prop_history or get_player_props, so an agent must infer the boundary rather than being told it.

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 to ... before a game' gives a clear situational trigger, and the 10-credit cost plus the compliance clause create real usage constraints. However, no exclusion or alternative is offered — an agent is not told when to prefer get_prop_history, get_player_props or get_line_movement instead, which is the main gap for a lineup with many overlapping prop tools.

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.

Resources

Need Help?