Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose substantive behavior: it names the components of the returned clause and, notably, the fallback to the market TITLE when the clause says "the time range specified in the title", with a concrete example (15-minute Chainlink TWAP family). However, it says nothing about failure behavior when no settlement clause is found, whether the result is cached, or its structure/completeness beyond the truncated field list.

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 definition is a single sprawling run-on sentence that nests parenthetical caveats inside parenthetical caveats, and it is truncated mid-token ("comparison_ba"), meaning the reader never receives the complete field list. The verb and resource are correctly front-loaded, but the sentence and the cut-off ending cost real clarity.

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 two-parameter tool with no output schema and no annotations, the description must explain what comes back, and it largely does by enumerating the clause components and the title-fallback rule. The truncation and the absence of any not-found or error behavior are the remaining gaps.

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 coverage is 100% and both parameters are documented upstream, including the polymarket vs polymarket-us distinction and the slug/URL vs ticker forms, so the schema already carries the weight. The description restates the venue scope (.com/.us, Kalshi) and confirms only a single market is accepted, but adds no format or validation detail beyond the schema.

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+resource: "Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market", and then enumerates the exact sub-fields returned (source, clock time + timezone, precision, comparison basis). That is far more specific than the tool name alone. It stops short of naming siblings such as resolution_diff or archive_compare, so an agent must infer that this is the single-market variant.

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?

The word "single" is the only scoping signal, implying this is not the multi-market diff/compare path, but no alternative is named and no conditions are given for choosing between this and resolution_diff or archive_compare. There is also no guidance on when this tool is inappropriate (e.g. market not found, unsupported venue).

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.