Skip to main content
Glama

Sharp price moves

price_moves
Read-onlyIdempotent

Lists prices that have just fallen hard compared with where they were trading a short while ago (often called steam moves). Most recent first; each row has the old price, the new price and the size of the fall in percent. Out of the box it looks back 10 minutes and keeps falls of 5% or more; raise max_age_sec or drop min_drop_pct for a wider net. Can be restricted by sport, by market (moneyline, spread, total, team_total) and by period. Counts as one request per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "price_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'live' for in-play moves, 'prematch' for moves before kick-offlive
limitNoMaximum number of rows to return
sportNoRestrict to one sport (id or name); leave out to cover every sport
marketsNoOnly these markets; leave out for all
periodsNoOnly these periods (0 = full game); leave out for all
max_age_secNoHow far back to look, in seconds
min_drop_pctNoSmallest fall, in percent, that counts
response_formatNo'detailed' adds the no-vig price, start time, score and an is_live flagconcise

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, open-world and idempotent behavior, and the description adds genuinely new facts: results are ordered most recent first, each row carries old price, new price and percent drop, and each call consumes one request against a quota. That quota cost is exactly the kind of operational context annotations cannot express. It does not discuss latency, caching or empty-result behavior, keeping it below a 5.

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?

Three dense sentences: what it is, what comes back, then how to tune and restrict it. Defaults and the widening levers are front-loaded, and the closing quota note earns its place as cost information. No filler or redundancy with the schema.

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 eight all-optional parameters and no output schema, the description carries the return-value burden and does so by describing ordering and the per-row fields, while the schema handles the detailed-mode extras. Defaults, cost and the filtering surface are all present, so an agent has enough to call it correctly on the first attempt.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond restating fields by explaining the interaction of the two threshold parameters as the way to widen or narrow the net, and by confirming the sport/market/period restrictions are optional. It adds no syntax detail for the sport identifier (id vs name) beyond what the schema already says, so it is not a 5.

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 — prices that have fallen sharply — and pins the concept down with the domain term 'steam moves', a default lookback window and a default drop threshold. The behavior is unmistakably distinct from a general odds/price listing tool like match_prices or upcoming_lines, so an agent can route correctly without opening the 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?

Gives concrete tuning guidance ('raise `max_age_sec` or drop `min_drop_pct` for a wider net') and lists the restriction dimensions, which tells the agent how to widen or narrow a query. It stops short of stating when to prefer this over siblings such as match_prices, and names no exclusions, so it is clear context rather than full routing guidance.

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.

Resources