StrikerAPI

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: 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 soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
`game_id`	Yes	Match id.
`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.5/5.0

Behavior5/5

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

Annotations already declare this as a safe idempotent read, so the description correctly focuses on what they cannot express: the snapshot cadence (daily, hourly for matches within four days), the 10-credit cost, and a hard compliance boundary against staking or betting advice. These are exactly the operational facts an agent needs before calling a priced data endpoint.

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 plus a short constraint clause, roughly fifty words, with the purpose front-loaded and the cost and compliance facts placed where they will be read before invocation. Nothing is redundant.

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 structure need not be explained; the description instead supplies the parts the schema cannot: cost, capture frequency, and the missing-data caveat that identical consecutive captures are collapsed. For a read-only historical endpoint this is complete.

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% and each parameter is already documented, including the dedup behavior of all_snapshots, so the schema carries the load. The description's cadence detail indirectly clarifies why all_snapshots exists, but it adds no explicit guidance on league/provider selection or game_id format. Baseline 3 is appropriate.

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?

States a specific verb and resource ('see how a match's line moved before kick-off') and enumerates exactly what is returned: pre-game snapshots of three-way moneyline, handicap and total per sportsbook. This clearly separates it from get_odds (current prices) and get_prop_history (player props) without the agent needing to open any schema.

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?

The opening 'Use to see how a match's line moved before kick-off' sets the usage context well, and the trailing prohibition ('never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook') is an explicit when-not-to-use constraint. It stops short of naming a sibling alternative for current prices (e.g. get_odds), so it is clear but not fully contrastive.

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

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