Skip to main content
Glama

FastballAPI

Line movement

get_line_movement
Read-onlyIdempotent

Use to see how a game's line moved before first pitch: our pre-game snapshots of each sportsbook's moneyline, run line 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 mlb. One of: mlb, ncaabase.
game_idYes
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, yet the description still adds real context: a 10-credit cost, the snapshot cadence (daily, hourly for the next four days), and a scope disclaimer that no wagering is placed or tracked. It does not discuss result limits or pagination, which keeps it from a 5.

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?

The purpose is front-loaded in the first clause, followed by scope, cadence, cost and a disclaimer, in a sensible order. The parenthetical cadence sentence is dense but earns its place; nothing is redundant.

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 strong annotations, the description only needs to cover scope, cost and cadence, all of which it does. It leaves open whether pre-game snapshots are available for finished or historical games, a minor gap for a tool explicitly bounded to 'before first pitch'.

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 75%, so most parameters are already documented, and the description adds meaningful cadence context that explains why all_snapshots matters (hourly captures vs. a daily baseline). It does not explain game_id's expected format or clarify how provider interacts with the default all-book aggregation, so it does not compensate fully for the remaining coverage gap.

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 states a specific verb and resource ('see how a game's line moved before first pitch') and enumerates the markets covered (moneyline, run line, total), which separates it from player-level movement tools like get_prop_movement. It stops short of naming that sibling outright, so the differentiation is inferred from 'a game's line' 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 first pitch' gives a clear situational trigger and a temporal boundary (pre-game only). There is no explicit when-not guidance or named alternative such as a current-odds tool, so the agent must infer that get_odds/get_market_odds cover live prices.

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.