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: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

Input Schema

Name	Required	Description
`league`	No	League. Defaults to mlb. One of: mlb, ncaabase.
`game_id`	Yes
`provider`	No	One sportsbook, e.g. DraftKings.
`all_snapshots`	No	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.

Output Schema

Name	Required	Description	Default
`game`	Yes
`note`	No
`movement`	Yes
`snapshots`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

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"
+}

First observedOct 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With annotations already covering read-only/idempotent safety, the description adds genuinely new operational facts: snapshot cadence (daily, then hourly for games within four days) and a 10-credit cost per call. It also discloses a policy constraint (never compute stakes/payouts, recommend bets, or route to a sportsbook) that no structured field conveys.

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?

Two sentences, no filler: purpose and data scope first, then cost and policy limits. Every clause carries information an agent cannot get from the schema or annotations.

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?

Output schema exists, so return values need no explanation, and annotations cover safety; the description fills the remaining gaps (cost, cadence, use limits). Minor omissions: no hint about behavior when no pre-game snapshots exist and no explicit pointer to get_odds for current lines.

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 75%, so the baseline is the schema itself; the description still adds meaning by explaining the capture cadence, which is what makes all_snapshots' 'every hourly capture' interpretable. game_id remains undocumented in prose, so it is not fully compensatory.

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?

States a specific verb and resource ('see how a game's line moved before first pitch') and enumerates the data returned: per-book snapshots of moneyline, run line and total. The phrase 'moved' and the snapshot framing implicitly separate it from get_odds, but no sibling is named explicitly.

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 clear use context, and the credit cost plus the prohibition on stake/payout/bet-recommendation work sets a firm boundary on legitimate use. No explicit when-not condition or named alternative (e.g. get_odds for current prices) is provided.

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

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