Skip to main content
Glama

Prediction market movers

prediction_market_movers
Read-only

Find prediction markets with the biggest odds changes. Returns markets where probabilities shifted the most in a given timeframe — early signal for breaking news or sentiment shifts. Costs $0.005 USDC 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": "prediction_market_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (max 25)
categoryNoFilter by category
directionNoFilter: up, down, bothboth
timeframeNoTimeframe: 1h, 6h, 24h24h
min_volumeNoMinimum total volume in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world profile, so the description's main added value is the explicit '$0.005 USDC per call' cost, which is exactly the kind of behavioral detail annotations cannot convey. It also discloses the return shape conceptually (markets with the largest probability shifts), though it says nothing about ordering, result caps, or pagination.

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 short sentences in a purposeful order: what it does, what it returns and why that matters, then cost. Every sentence carries information an agent needs; nothing is redundant with the name or title.

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 does sketch the return concept, and with all five parameters optional and fully documented in the schema, the invocation surface is clear. The main residual gap is that the actual fields of each returned market are left unspecified, which an agent would want when deciding between this and prediction_market_odds.

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 every parameter (limit, category, direction, timeframe, min_volume) is already documented in structured data. The description's only echo is 'in a given timeframe,' which adds no syntax or constraint detail beyond the schema. 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?

States a specific verb and resource — 'Find prediction markets with the biggest odds changes' — and clarifies the ranking criterion (largest probability shift in a timeframe). This distinguishes it in spirit from siblings like prediction_market_odds or prediction_markets_trending, but it never names or contrasts those siblings explicitly.

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?

It gives a use case ('early signal for breaking news or sentiment shifts') which implies when to reach for it, but offers no when-not guidance and no routing to alternatives such as prediction_market_sentiment or prediction_markets_trending. An agent must infer the boundary 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.

Resources