Skip to main content
Glama

MCPFax Macro & Market Intelligence

by com.mcpscores
OverviewDiscussionsAdmin

Cross-venue market search

prediction_market_search
Read-onlyIdempotent

Find a prediction market by question text across two venues at once — Polymarket (USDC, real money) and Manifold (MANA, play money) — returning a single normalised list with the venue, its currency, the question, the YES probability, volume, end date and a direct URL, plus a per-venue status so a venue that failed is visible rather than silently dropped. Use it when you know the question but not the venue or the id. Kalshi is deliberately not included: its API answers Cloudflare Workers with HTTP 429 on every attempt. Costs $0.008 USDC per call via x402 on Base; an unpaid call returns the payment challenge instead of data, and a call that returns no data is never settled so it costs nothing. Equivalent HTTP route: GET /prediction-markets/search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoQuestion text to search for (required) Example: 'fed rate'.
venuesNoComma-separated subset of polymarket,manifold Example: 'polymarket,manifold'.
limit_per_venueNoResults per venue, 1-20 (default 5) Example: '5'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit_per_venue / examples
      Added value: +[
+  5
+]
    • addedInput schema / properties / q / examples
      Added value: +[
+  "fed rate"
+]
    • addedInput schema / properties / venues / examples
      Added value: +[
+  "polymarket,manifold"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive. The description adds substantial behavior: cost per call, payment challenge on unpaid calls, no charge for empty results, per-venue status visibility, and the deliberate exclusion of Kalshi. No contradiction with annotations.

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?

The description is dense but every sentence carries value: purpose, return format, usage condition, exclusion, cost, payment behavior, and HTTP route. It is front-loaded with the core purpose and avoids redundancy.

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?

For a complex tool with no output schema, it explains return structure (normalised list with venue, currency, question, YES probability, volume, end date, URL, per-venue status), failure handling, cost, and alternatives. An agent has all necessary context to call it correctly.

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% and each parameter already has descriptions and examples. The description does not materially extend parameter meaning beyond the schema, though it does imply q is required via usage phrasing. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Find' and the resource 'prediction market by question text', specifies the two venues (Polymarket and Manifold), and distinguishes it from sibling single-venue tools by emphasizing the cross-venue normalization and unified output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'when you know the question but not the venue or the id.' Also provides a clear exclusion (Kalshi) with a technical reason, and mentions cost/behavior that informs invocation decisions.

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

All MCPFax Macro & Market Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources