Skip to main content
Glama

DunkAPI

Line movement

get_line_movement
Read-onlyIdempotent

Use to see how a game's line moved before tip-off: our pre-game snapshots of each sportsbook's moneyline, spread and total (captured once a day, and every hour for games in the next four days). Costs 10 credits. Prices are market information; no tool places, accepts or tracks wagers.

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>"
    },
    "name": "get_line_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl.
game_idYesGame id.
providerNoOne sportsbook, e.g. DraftKings.
all_snapshotsNoEvery hourly capture. By default a capture identical to the one before it is left out (the latest is always kept), which keeps every move and its time.

Output Schema

NameRequiredDescriptionDefault
gameYes
noteNo
movementYes
snapshotsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nba. One of: nba, wnba, ncaam, ncaaw."New value: +"League. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nba",
      -  "wnba",
      -  "ncaam",
      -  "ncaaw"
      -]New value: +[
      +  "nba",
      +  "wnba",
      +  "ncaam",
      +  "ncaaw",
      +  "nbl"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / all_snapshots
      Added value: +{
      +  "description": "Every hourly capture. By default a capture identical to the one before it is left out (the latest is always kept), which keeps every move and its time.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description adds genuinely new behavior: capture cadence (daily, hourly for games within four days), a 10-credit cost per call, and a scope disclaimer that no tool places or tracks wagers. These details about data freshness and quota are exactly the kind of context annotations cannot express; only minor gaps remain (e.g. behavior for games with no snapshots).

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 is front-loaded before the colon, then cadence, then cost, then scope disclaimer — a sensible information ordering with no filler. The closing wagering disclaimer is somewhat tangential to invoking the tool, but it plausibly earns its place as a guardrail against misuse.

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 an output schema present and full parameter coverage, the description only needs to supply cost, freshness, and scope, all of which it does. It stops short of describing edge cases such as a game with no recorded snapshots or whether a provider filter narrows the response, which an agent might want before spending 10 credits.

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%, including the all_snapshots dedup default, so the schema already carries parameter meaning and baseline 3 applies. The description reinforces that snapshots are per-sportsbook (relevant to provider) and are pre-game only, but adds no unused-parameter, required-parameter, or format guidance beyond the schema.

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?

"Use to see how a game's line moved before tip-off" gives a specific verb (see movement) and resource (pre-game line snapshots) with the data types named (moneyline, spread, total). It implicitly separates itself from current-odds siblings by stressing "pre-game snapshots" and "before tip-off," but never names an alternative tool such as get_prop_movement or get_market_odds, so sibling differentiation is inferred rather than stated.

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 how a game's line moved before tip-off" states the condition that selects this tool, and the phrase "pre-game snapshots" rules out live in-game pricing. There is no explicit exclusion clause or named alternative for agents deciding between this and the odds/prop-movement tools, which keeps it below a 5.

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.