Skip to main content
Glama

Antigravity x402 & MCP Gateway

scan_prediction_market_arb

[0.008000 USDC via x402] Scans active Polymarket Gamma CLOB and CFTC-regulated Kalshi v2 event contracts in real time, computing exact Decimal implied probabilities, market-maker vig %, top liquid contracts, and fuzzy-matched cross-venue pairs with probability divergence and gross arbitrage edge %.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum contracts per venue and cross-venue arbitrage pairs to return (1 to 25, default 8).
queryNoOptional case-insensitive topic filter (e.g., 'Fed', 'Bitcoin', 'Trump', 'NATO', 'recession', or '' for top volume).
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.008000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most decision-relevant facts: this is a paid call at 0.008000 USDC via x402, it queries two live venues, and it computes derived metrics rather than returning raw books. It stops short of stating read-only nature explicitly, rate limits, data staleness, or what a caller receives when the payment signature is omitted beyond the schema's brief note.

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?

The price tag is correctly front-loaded in brackets, followed by a single sentence that packs venue scope and output metrics. It is dense but every clause adds information; the only mild cost is the run-on list of computed fields, which could be trimmed or split for scanning.

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 paid, multi-venue aggregation tool with no output schema, the description conveys which venues are hit, what is computed, and the payment model, which is enough to decide whether to call it. It would be stronger with a hint about response shape (per-venue lists plus matched pairs) or payment failure behavior, but nothing essential to invoking it is missing.

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 limit, query, and the payment signature are already fully documented with types, ranges, and defaults. The description adds no additional semantics for limit or query and only restates the price tied to the payment parameter, so the baseline of 3 applies.

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 names a specific verb and two concrete resources ("Scans active Polymarket Gamma CLOB and CFTC-regulated Kalshi v2 event contracts") and enumerates the computed outputs: implied probabilities, market-maker vig, cross-venue divergence, and arbitrage edge. No sibling tool in the catalog touches prediction-market arbitrage, so the scope is unambiguous without opening the schema.

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?

Usage is only implied by the phrasing "arbitrage edge %" and "top liquid contracts" – an agent can infer the intent is cross-venue arbitrage discovery or probability research. There is no explicit when-to-use statement, no exclusions (e.g., not for single-venue pricing), and no prerequisites beyond the payment note.

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.