EndzoneAPI

Line movement

get_line_movement

Read-onlyIdempotent

Use to see how a game's lines moved: each bookmaker's hourly snapshots where a line changed, plus the latest (all_snapshots for every capture). Most expensive tool (25 cr); use get_odds (10 cr) if you only need opening, closing, or current lines. 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
`game_id`	Yes	Game id
`bookmaker`	No	Bookmaker key filter
`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_id`	Yes
`kickoff`	Yes
`movement`	Yes
`away_team`	Yes
`home_team`	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"
+}

Changed1 schema field changedOct 8, 2026
- addedOutput schema / properties / movement / additionalProperties / items / properties / source
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive; the description adds what annotations cannot: the 25-credit cost, the default dedup behavior (identical captures dropped, latest always kept), and a hard compliance constraint forbidding stake/payout math or betting recommendations. That is materially useful behavioral context.

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?

Front-loaded with the purpose, then cost/alternative, then the compliance rule; every sentence carries information. The opening sentence is dense with nested parentheticals but not padded.

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-shape explanation is unnecessary. Given the tool's cost, alternatives, default filtering, and legal constraints are all covered, an agent has everything needed to decide and call correctly.

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 game_id, bookmaker filter, and all_snapshots are all documented in the schema, including the dedup semantics of all_snapshots. The description restates all_snapshots but adds no syntax or format detail beyond the schema, so 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: how a game's lines moved, returning each bookmaker's hourly snapshots where a line changed plus the latest. The scope (per-bookmaker, change-only by default) makes it distinguishable from odds-related siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: 'use get_odds (10 cr) if you only need opening, closing, or current lines', with a cost comparison that makes the trade-off concrete. It also explains when to pass all_snapshots rather than relying on the default.

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

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