Skip to main content
Glama

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; 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": {
      "bout_id": "<bout_id>"
    },
    "name": "get_line_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to mma. One of: mma, pfl, bellator.
bout_idYesFight 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
boutYes
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/idempotent, so the bar is lower, and the description adds genuinely useful behavior beyond them: a 10-credit cost, the capture cadence (daily from October 2026, hourly in the four days before a fight), and an explicit statement that no wagers are placed or tracked. The one gap is that nothing is said about what happens when no snapshots exist for a bout.

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 and cadence are front-loaded, and the credit cost is placed prominently where an agent will see it. The closing sentence about not placing or tracking wagers is defensive scoping rather than invocation-critical, but it is short and plausibly load-bearing for a betting-adjacent tool.

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?

With full schema coverage, a defined output schema, and strong annotations, the definition supplies exactly the extra context an agent needs: cost, temporal resolution, and scope limits. Nothing required to select or invoke the tool is missing.

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%, so the schema already documents league, bout_id, provider and all_snapshots. The description reinforces the dedupe semantics ('our snapshots ... from first capture to fight day') but adds no format, default, or provider-selection detail beyond what the schema states, so baseline 3 applies.

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 names a specific resource and verb ('see how a fight's line moved') and specifies the underlying data ('our snapshots of each posted moneyline, from first capture to fight day'), which implicitly separates it from a current-odds tool like get_odds. It stops short of naming any sibling explicitly, so the differentiation is inferred 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use to see how a fight's line moved before the bell' supplies a use context, but there is no explicit when-not guidance, no mention of how it differs from get_odds (current lines), and no prerequisites described. The agent can infer it is for historical movement rather than live prices, but must do the work itself.

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.