Skip to main content
Glama

Line movement

get_line_movement
Read-onlyIdempotent

Use to see how a match's line moved before kick-off: our pre-game snapshots of each sportsbook's three-way moneyline, handicap and total (captured once a day, and every hour for matches 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 soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
game_idYesMatch 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. 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"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive), the description adds a concrete cost ('Costs 10 credits'), the snapshot cadence and the temporal horizon, and a scope disclaimer that no tool places or tracks wagers. Cost and data-freshness are the two traits an agent needs before spending a call here and are absent from the structured fields.

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?

Three compact sentences, front-loaded with the purpose, then the data granularity, then the cost and scope caveat. Every sentence carries distinct information and none restates the tool name or annotations.

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-shape explanation is rightly omitted. With cost, market coverage, cadence, time window and a wagering-scope disclaimer all present, an agent has everything needed to decide and call correctly.

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 about what a 'snapshot' is (daily vs hourly captures), which contextualizes the all_snapshots flag beyond the schema's dedup note. It does not touch league defaults or provider semantics, which the schema already handles.

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?

The description names a specific verb and resource ('see how a match's line moved before kick-off') and pins the exact data covered: pre-game snapshots of each sportsbook's three-way moneyline, handicap and total. The 'pre-game snapshots' framing separates it from current-odds siblings like get_odds/get_market_odds and from get_prop_movement, which covers player props.

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?

Usage context is clear: it is for historical pre-game line movement, with capture cadence spelled out (daily, hourly for matches within four days), which tells the agent when the data will and will not be granular. No sibling is named as an explicit alternative and there is no 'use X instead when...' exclusion, so it stops short of 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.