Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_prediction_markets

Scan Polymarket, Kalshi, and Manifold prediction markets to compare normalized YES/NO probabilities, spreads, and cross-venue arbitrage divergences.

Instructions

Paid x402 API ($0.008 USDC on Base): Live prediction market scanner aggregating Polymarket, Kalshi, and Manifold Markets with normalized YES/NO probabilities, spreads, and cross-venue arbitrage divergences.

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

Input Schema

NameRequiredDescriptionDefault
qNoOptional keyword search across market questions (e.g. bitcoin, fed, eth)
limitNoMax markets returned (1-100, default 20)
platformNoFilter platforms: polymarket, kalshi, manifold, or all
minLiquidityNoMinimum market liquidity threshold

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden – and it does disclose the most decision-critical trait: this is a paid x402 endpoint costing $0.008 USDC on Base, which an agent must know before invoking. It also reveals data provenance (three live venues). It stops short of rate limits, per-call vs per-session billing, pagination, or failure behavior.

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 dense sentence with the cost/payment model front-loaded, which is the right priority ordering. Nothing is padded, though the second half packs venues, fields, and arbitrage into one long clause that reads more as a list than prose.

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 zero-required-parameter read tool with a fully described schema and no output schema, the description covers what the tool does, what it costs, where data comes from, and roughly what comes back. Remaining gaps (payment mechanics, result freshness, error/empty-result behavior) are secondary for correct invocation.

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 all four parameters (q, limit, platform, minLiquidity) are already documented in the schema with examples and ranges. The description adds no parameter-specific meaning such as how liquidity thresholds are computed or how cross-venue normalization handles mismatched market titles. 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?

"Live prediction market scanner" names a specific verb+resource, and the description enumerates the three aggregated venues (Polymarket, Kalshi, Manifold) plus the returned payload (normalized YES/NO probabilities, spreads, arbitrage divergences). It does not name a sibling tool or explicitly contrast itself with verifystack_arb_net_profit, so an agent must infer the boundary, but the function itself is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative named. The only implied usage is that this is a discovery/scanning step, and nothing tells the agent whether to call this before or instead of verifystack_arb_net_profit.

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