Skip to main content
Glama

Prediction market odds

prediction_market_odds
Read-only

Get current odds for a prediction market. Search by market slug, ID, or natural language query like 'bitcoin 100k' or 'fed rate cut'. Returns probabilities, volume, liquidity, and outcome prices. Costs $0.002 USDC per call.

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": {
      "query": "<query>"
    },
    "name": "prediction_market_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesMarket slug, ID, or search query (e.g. 'bitcoin 100k', 'fed rate cut', 'trump')

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 declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description earns credit for adding the per-call price ('$0.002 USDC per call'), a genuine behavioral trait an agent needs for cost-aware tool selection. It also lists the payload fields returned. It stops short of describing failure modes (invalid slug vs. no-match query) or freshness of the odds.

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?

Four short sentences, front-loaded with purpose, then accepted inputs, then return fields, then cost. Nothing is padded and the cost — the highest-value fact — is placed where it is easy to scan.

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?

For a one-parameter read tool with no output schema, the description covers what is returned and what it costs, which is sufficient to call it correctly. The main gap is the absence of any signal distinguishing it from closely related prediction-market tools in the same server.

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?

Single required parameter with 100% schema description coverage, so the schema already documents `query` fully, including the same example strings. The description restates the accepted input types but adds no new syntax, format, or disambiguation rules beyond the schema — baseline 3.

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+resource ('Get current odds for a prediction market') and enumerates what comes back (probabilities, volume, liquidity, outcome prices), so the agent knows exactly what this returns. It does not differentiate itself from the many prediction-market siblings (polymarket_quote, prediction_market_aggregator, prediction_market_events), which is the only thing keeping it from a 5.

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 clarifies acceptable input forms (slug, ID, or natural-language query) and gives concrete example queries, which helps an agent phrase a call. But there is no when-to-use-vs-alternatives guidance and no exclusions, despite a crowded sibling namespace of prediction-market tools where routing guidance would be most valuable.

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