FighterAPI

Line movement

get_line_movement

Read-onlyIdempotent

Use to see how a fight's line moved before the bell: our snapshots of each posted moneyline, from first capture to fight day (once a day from October 2026, and every hour in the four days before). 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 mma. One of: mma, pfl, bellator.
`bout_id`	Yes	Fight 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
`bout`	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?

Beyond annotations (readOnly/idempotent), it discloses credit cost (10), snapshot cadence (daily from October 2026, hourly in the four days before), and deduplication behavior that keeps every move and its time. It also states the compliance boundary on what may be done with prices, which annotations cannot convey.

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, purpose and sampling cadence first, cost and compliance second. Every clause carries information an agent would otherwise have to guess.

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?

Output schema exists, so return shape need not be described; annotations cover safety; all four params are schema-documented. The description adds the cost, sampling policy and compliance limits that structured fields do not carry.

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 100%, so the schema already documents league, bout_id, provider and all_snapshots. The description only indirectly touches all_snapshots by explaining snapshot density and default deduplication; it adds no semantics for provider or league beyond the schema. Baseline 3 applies.

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 fight's line moved') plus the exact data granularity (snapshots of each posted moneyline from first capture to fight day). This clearly separates it from get_odds, which by name covers current pricing rather than historical movement.

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?

Gives clear context for use ('before the bell', historical movement) and hard exclusions drawn as compliance guardrails: never compute stake/payout/profit, recommend a bet, or send the user to a sportsbook. It does not explicitly name get_odds as the alternative for current lines, leaving that inference to the agent.

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

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