puntersedge

Sports price movements

sports_movements

Read-onlyIdempotent

How a sport's prices have moved since a time (default the last 24 hours), per bookmaker and outcome. Costs 5 credits. Plan: Standard and above.

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": {
      "sport_key": "<sport_key>"
    },
    "name": "sports_movements"
  }
}

Input Schema

Name	Required	Description	Default
`since`	No
`market`	No		h2h
`min_delta`	No
`sport_key`	Yes	Sport key from sports_list, e.g. afl, nrl, nba or soccer_epl. An unknown key is answered with the valid ones.
`bookmakers`	No	Only these bookmaker keys, e.g. ["tab", "sportsbet", "ladbrokes_au"]. Default: every book. An unknown key is refused free of charge with the list of valid keys.

Output Schema

Name	Required	Description	Default
`data`	Yes	The API response, with links and empty fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / sport_key / description

Previous value: -"Sport key from sports_list, e.g. afl, nrl, nba or epl. An unknown key is answered with the valid ones."New value: +"Sport key from sports_list, e.g. afl, nrl, nba or soccer_epl. An unknown key is answered with the valid ones."

First observedOct 22, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so safety needs no restating. The description adds two pieces of genuinely new operational context: a 5-credit cost and a plan-tier requirement. Remaining gaps are volume/pagination behavior and how large result sets are returned.

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?

Two short sentences with the core behavior front-loaded and the cost/plan constraints appended compactly. Nothing is redundant, though the terse 'Costs 5 credits. Plan: Standard and above.' reads as a fragment rather than structured metadata.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the return shape needs no explanation, and cost plus plan eligibility are covered. But for a 5-parameter analytical tool, the unexplained min_delta and market parameters leave a real hole in what an agent needs before calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40% — only sport_key and bookmakers carry descriptions. The description clarifies 'since' (default last 24 hours) but leaves 'market' (enum with a default) and especially 'min_delta' completely unexplained; an agent cannot tell whether min_delta is a percentage, a price delta, or an absolute odds shift, nor what units it uses.

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 states a specific resource and computation: price movements for a sport since a given time, broken down per bookmaker and outcome. That is clearly distinct from sports_odds (current prices) or sports_results, though no sibling is named explicitly, so the agent must infer the split itself.

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 is implied by the stated default window (last 24 hours) and the 'since' parameter, and the eligibility gate ('Plan: Standard and above') tells the agent when the tool is unavailable. However, nothing says when to prefer this over siblings like price_history, odds_changes or market_movers, which cover overlapping ground.

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

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