Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: per-venue differences between polymarket.com, polymarket.us, and Kalshi, a TITLE fallback for the Chainlink TWAP market family, and precision variants such as "1-minute candle close" versus "twap_60s_lookback". It does not state whether the call is read-only, what happens when no settlement clause is found, or what the response looks like, and the truncation cuts off the remaining behavioral disclosure.

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 content is delivered as one long run-on sentence dense with parenthetical asides, and it terminates mid-word at "comparison_ba", which reads as a broken or truncated definition. The core extraction targets are front-loaded, but the structure makes the scope hard to parse and signals an incomplete artifact.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must explain what a caller gets back, and it does not — the sentence breaks off before finishing the field list. For a tool whose entire value is a structured settlement-clause extraction, an agent cannot tell the full returned shape or the failure mode when a clause is missing. The disclosure of venue and fallback rules is genuine but insufficient for the tool's complexity.

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%, and the enum values for venue are explained in detail upstream, including the distinction between polymarket.com and the CFTC-regulated polymarket.us and the kalshi ticker fallback. The description adds little parameter-level detail beyond restating the venue families, so the baseline of 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?

The description opens with a specific verb and resource ("Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market") and enumerates the extractable fields: publishing source, clock time plus timezone, and computation precision. It clearly differs from resolution_diff by emphasizing extraction of one market's clause rather than comparison. It falls short of 5 because the sentence is cut off mid-word ("comparison_ba"), leaving the full output scope ambiguous.

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 statement of when to choose this tool over the sibling resolution_diff, nor any when-not guidance or prerequisite conditions. The only conditional logic present (falling back to the market TITLE when the clause references "the time range specified in the title") describes internal behavior, not caller decision-making. Usage must be inferred entirely from the one-line purpose.

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.