DunkAPI

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
`league`	No	League. Defaults to nba. One of: nba, wnba, ncaam.
`market`	Yes	The market: player_points (points), player_rebounds (rebounds), player_assists (assists), player_threes (three-pointers made), player_points_rebounds_assists (points + rebounds + assists), player_blocks (blocks), player_steals (steals), player_points_rebounds (points + rebounds), player_points_assists (points + assists), player_rebounds_assists (rebounds + assists), player_double_double (double-double (over = yes)), player_triple_double (triple-double (over = yes))
`game_id`	Yes	Game id.
`bookmaker`	No	One book's captures, e.g. draftkings.
`player_id`	Yes	Player id (e.g. 3945274) 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?

Beyond the read-only and idempotent annotations, it discloses oldest-first book-by-book captures, the exact line_change calculation, variable capture counts, and a 10-credit cost. These details set useful expectations about output interpretation, data coverage, and invocation cost.

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?

The purpose is front-loaded, and each following sentence contributes a distinct detail: calculation, coverage variability, cost, or usage restrictions. It is dense but contains no filler or repetition of the parameter list.

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?

Together with the fully described input and output schemas and read-only annotations, this supplies nearly everything needed to invoke and interpret the tool. The main remaining gap is explicit routing among get_line_movement, get_prop_history, and get_player_props for adjacent requests.

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%, including enums, defaults, and the player_id source, so the baseline is 3. The description's references to the game, book, and individual player add context but no substantial input syntax or selection semantics beyond those schema descriptions.

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 opening clause gives a specific resource and scope: movement of one player's prop line before a game, across every held capture. It does not explicitly distinguish this from similarly named siblings such as get_line_movement or get_prop_history, so it is clear rather than fully differentiating.

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 see" supplies a clear pre-game, single-player use case, and the final sentence constrains how price information may be used. There is no guidance on when another sibling is preferable or on prerequisites beyond the schema's player_id pointer.

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

All DunkAPI 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.