Skip to main content
Glama

Resolution Audit

resolution_audit
Read-onlyIdempotent

Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title", e.g. Polymarket's 15-minute Chainlink TWAP family), the precision of the computation (e.g. "1-minute candle close" vs "60-second trailing average" vs "twap_60s_lookback"/"twap_30s_lookback" vs "election outcome"), comparison_basis, what is compared to what (end_average_vs_start_average | close_vs_open; orthogonal to precision, since venues can share this comparison shape while computing each endpoint differently), the evidence standard (official_source | consensus_reporting | any_credible_report | unspecified), and void_handling (cancellation/postponement settlement, reused verbatim from bet_research's cancellation_rule detector, not re-derived). Parses Polymarket's description field (fetched via polymarket_market, or via polymarket_us_search for the .us venue) or Kalshi's rules_primary + rules_secondary fields (fetched via kalshi_market) with regex + a small vocabulary, no LLM pass, so an unusual clause reports confidence:"low" rather than a guess. Pass market as a Polymarket slug/URL (either venue) or a Kalshi market ticker (e.g. "KXBTCD-26SEP1317-T66999.99"); a Kalshi EVENT ticker (e.g. "KXBTCD-26SEP1317") also works, it picks one representative market under that event, since the settlement mechanism is normally shared across all strikes/legs in one event. Use this before treating a polymarket_kalshi_spread row as a real arbitrage: two ladders that look alike can settle on different sources (Polymarket.com's Chainlink TWAP stream vs Kalshi/Polymarket US's CF Benchmarks BRTI), at different times, or with a different lookback window, this tool is how you check. Pair with resolution_diff to compare two markets directly. KNOWN GAP: idiosyncratic phrasing that doesn't match the vocabulary returns confidence:"low" and evidence_standard:"unspecified" rather than an LLM-guessed answer.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue": "polymarket",
      "market": "bitcoin-above-70k-on-september-13-2026"
    },
    "name": "resolution_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueYesWhich venue to fetch the market from. "polymarket" is the offshore venue (polymarket.com); "polymarket-us" is the separate, CFTC-regulated polymarket.us venue, matched by slug via its own search (no exact-slug lookup exists upstream).
marketYesPolymarket (.com or .us) market slug or URL, OR a Kalshi market ticker (preferred) or event ticker (falls back to a representative market under that event).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / market / description
      Previous value: -"Polymarket market slug or URL, OR a Kalshi market ticker (preferred) or event ticker (falls back to a representative market under that event)."New value: +"Polymarket (.com or .us) market slug or URL, OR a Kalshi market ticker (preferred) or event ticker (falls back to a representative market under that event)."
    • changedInput schema / properties / venue / description
      Previous value: -"Which venue to fetch the market from."New value: +"Which venue to fetch the market from. \"polymarket\" is the offshore venue (polymarket.com); \"polymarket-us\" is the separate, CFTC-regulated polymarket.us venue, matched by slug via its own search (no exact-slug lookup exists upstream)."
    • changedInput schema / properties / venue / enum
      Previous value: -[
      -  "polymarket",
      -  "kalshi"
      -]New value: +[
      +  "polymarket",
      +  "kalshi",
      +  "polymarket-us"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses implementation behavior that matters for trust: regex plus a small vocabulary with 'no LLM pass', a low-confidence fallback instead of guessing, and a KNOWN GAP section stating what it will fail on. It also discloses an upstream dependency (fields fetched via polymarket_market / polymarket_us_search / kalshi_market) and a non-obvious input behavior where a Kalshi event ticker silently resolves to one representative market. The only missing pieces are rate limits and a clear statement of the returned shape.

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?

Information-dense and front-loaded with what it extracts, but it is a single long run-on paragraph dense with parentheticals and pipe-delimited enumerations, which makes scanning hard. Some clauses, such as the explanation of why comparison_basis is orthogonal to precision, add precision but inflate the sentence structure.

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 carries the burden of describing return content, and it does enumerate the fields returned plus the confidence/evidence_standard fallback values. What is absent is any indication of output format/structure, and the TITLE-fallback behavior for time-of-settlement is only illustrated by one example rather than stated as a rule.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already carries the baseline. The description still adds value by explaining accepted market identifier forms (slug, URL, Kalshi market ticker, event ticker) and, crucially, the event-ticker fallback rationale ('settlement mechanism is normally shared across all strikes/legs in one event').

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?

Opens with a specific verb and resource ('Extract the settlement clause of a single Polymarket ... or Kalshi market') and then enumerates exactly which attributes are extracted (source, clock time, precision, comparison_basis, evidence standard, void_handling). It also explicitly distinguishes its scope ('a single market') from resolution_diff, which 'compare[s] two markets directly'.

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?

Gives a concrete trigger condition ('Use this before treating a polymarket_kalshi_spread row as a real arbitrage') with the rationale, names the failure mode it prevents (different sources, times, lookback windows), and routes to the sibling 'resolution_diff' for the two-market comparison case.

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.