Skip to main content
Glama

NS Pros MCP Gateway

numverify__resolution_audit

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_ba

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": "numverify__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. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the shape of what is extracted (publisher of the settling number, clock time/timezone, precision of computation) including a useful fallback behavior where the time is taken from the market TITLE. It does not cover failure modes, whether missing clauses return null vs error, or any access/rate constraints, and the trailing truncation removes the final behavioral detail.

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

Conciseness2/5

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

The opening is front-loaded and dense with useful detail, but the single sentence is a runaway list and, critically, terminates mid-word at 'comparison_ba', so the definition is structurally incomplete. An agent reading it cannot know the full set of extracted fields.

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 and no annotations, the description must explain both behavior and returns; it partially does by naming the extracted fields. But the truncation leaves the return structure unfinished and there is no mention of error handling, so it is only marginally adequate for a tool whose whole value is the shape of its output.

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%, with venue enum values and the market slug/ticker format already documented in the input schema, so the baseline is 3. The description only restates the accepted venues and market forms rather than adding new meaning such as how a Kalshi event-ticker fallback resolves or what happens with ambiguous slugs.

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?

States a specific verb and resource: 'Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market', and enumerates the components it returns (source, clock time + timezone, precision). The intent is unmistakable, though the text cuts off mid-token at 'comparison_ba', leaving the final component undefined.

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?

The phrase 'single ... market' implies this is a per-market lookup rather than a bulk scan, and the venue coverage is stated. However, there is no explicit when-to-use versus alternatives, no guidance on what happens for markets lacking a settlement clause, and nothing about handling the fallback paths it mentions.

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.