Skip to main content
Glama
argon-x402-mcp-bridge

argon-x402-mcp-bridge

by Khanhtnq

polymarket_slippage_preflight

Read-only

Simulate Polymarket YES/NO order fills against live CLOB asks to estimate VWAP price and slippage before trading; also analyzes UMA resolution-rule edge cases.

Instructions

Live Polymarket Gamma + CLOB orderbook VWAP fill/slippage simulator & UMA Optimistic Oracle resolution-rule edge-case analyzer. Includes 3 free calls/day/IP; thereafter $0.01 Base USDC via x402 (payTo: 0xcbEDbeCC127a32217075Ff40f16Ec804aa1E0533, asset: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).

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": {
      "slug": "<slug>"
    },
    "name": "polymarket_slippage_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoOutcome token side to simulate buying (YES or NO)YES
slugYesPolymarket market slug or event slug
size_usdNoSimulated USD order size to walk against live CLOB asks (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the supplied readOnlyHint/openWorldHint annotations, the description discloses genuinely useful behavioral facts: it queries live external Polymarket data, is quota-limited to 3 calls/day/IP, and requires an x402 payment of $0.01 Base USDC with explicit payTo and asset addresses. This is exactly the kind of cost/quota/auth context the annotations cannot carry. It stops short of a 5 because latency, failure modes, and confirmation that no real order is placed are left implicit in the word 'simulator'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is only two sentences, and the capability statement is front-loaded, which is good. However, the second sentence is dominated by two long hex addresses and payment plumbing, and the first sentence stacks opaque modifiers ('Gamma + CLOB', 'VWAP fill/slippage', 'UMA Optimistic Oracle resolution-rule edge-case'). Dense but not efficiently structured for an agent skimming for the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of saying what comes back, and it does not – an agent cannot tell whether the result is a fill price, a slippage figure in bps, a per-level breakdown, or a UMA rule warning. It also does not say whether the UMA edge-case analysis always runs or is conditional. For a read-only, three-parameter tool the gaps are moderate rather than fatal, since the core input contract is fully specified.

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 slug, side, and size_usd are already fully documented with defaults and an enum. The description adds only indirect meaning ('walk against live CLOB asks' hints at how size_usd is consumed, and 'market slug or event slug' is already in the schema). Baseline 3 is appropriate 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: a 'VWAP fill/slippage simulator' that walks live Polymarket Gamma + CLOB orderbook asks, plus a 'UMA Optimistic Oracle resolution-rule edge-case analyzer'. That is far more concrete than the name alone. It loses a point because two distinct capabilities are welded together without saying whether the UMA analysis is automatic output or a separate mode, and the jargon density makes the core action harder to extract than necessary.

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, when-not-to-use, or alternative-routing guidance. The only contextual constraint given is commercial (3 free calls/day/IP, then paid), which bounds cost rather than telling the agent when this tool is the right choice. The intended use – pre-trade slippage estimation before buying an outcome token – must be inferred from the phrase 'simulated USD order size to walk against live CLOB asks'.

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