Skip to main content
Glama

Prediction movers

prediction_movers

Prediction markets moving now: the Polymarket markets whose odds moved most in the last 24 h (or 1 h / 1 week) among the ~500 most traded, with the move, price now, bid/ask, volume, link. $0.003

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": "prediction_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomarkets to return, 1-50 (default 20)
windowNowindow of the move (default 24h)
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.
min_volumeNominimum 24 h volume in USD (default 10000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the result shape (move, price now, bid/ask, volume, link) and the $0.003 price, which is genuinely useful, but it never states that payment is required, what happens on an unpaid call, or whether results are cached/sampled.

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?

A single front-loaded sentence delivers the subject, the ranking rule, the window choices, and the returned fields, with the price tacked on as a compact trailing token. It is dense and slightly run-on, but no sentence is wasted.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the returned fields, and the payment mechanics are covered by a thorough schema parameter description. The remaining gap is the paid-access flow itself (402 behavior, whether a preview is returned), which matters for a paywalled tool.

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 all four parameters are already documented, including defaults and the window enum. The description adds context that the universe is capped at the ~500 most traded markets, which reframes what limit and min_volume actually select, but adds no syntax or edge-case detail beyond the schema.

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 ranking criterion: Polymarket markets whose odds moved most over a chosen window, restricted to the ~500 most traded. That clearly separates it in spirit from prediction_odds or market_search, but the description never names the sibling it supersedes, so the agent must infer the distinction.

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?

Usage is implied by 'moving now' and by the window options, which tell an agent this is for surfacing recent momentum rather than a specific market lookup. There is no explicit guidance on when to prefer this over prediction_odds, no stated preconditions, and no exclusions such as non-Polymarket venues.

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