Agent Kiosk

prediction_markets

Read-onlyIdempotent

Search live prediction market odds and real-money implied probabilities from Polymarket and Manifold for crypto, macro, political, or tech events.

Instructions

Query live prediction market odds & real-money implied probabilities (%) from Polymarket and Manifold Markets for any crypto, macro-economic, political, or technology event.

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_markets"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of markets to return (1-15, default: 5)
`query`	Yes	Event or topic to search (e.g., 'bitcoin', 'fed rate', 'AI', 'election')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.5.0Oct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: the data is live, sourced from two named venues, and expressed as real-money implied probabilities in percent. It stops short of noting refresh cadence or coverage limits per venue.

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?

A single front-loaded sentence that packs verb, data type, sources, and domain coverage with no filler or redundancy. Nothing could be removed without losing information.

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 states the return units (percent implied probability) and the sources, which is the key missing piece for interpreting results. It could go further by describing result ordering or how multiple markets per query are ranked.

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 both parameters (query, limit) are fully documented with examples and bounds in the schema. The description adds no parameter-level detail of its own, which is the expected baseline when the schema does the heavy lifting.

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?

Specific verb (Query) plus a precisely scoped resource (live prediction market odds & implied probabilities) with named sources (Polymarket, Manifold) and supported domains (crypto, macro, political, tech). No sibling tool covers prediction markets, so it is unambiguously distinguishable.

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?

The description implies when the tool is useful (any event with market-implied odds) but gives no explicit when-to-use vs. alternatives, no exclusions, and no guidance on how it relates to siblings like domain_intel or social_search. Usage is inferable rather than stated.

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