Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the disclosure burden. It usefully reveals a non-obvious behavioral rule — falling back to the market TITLE when the clause says "the time range specified in the title" — but does not say what happens when no settlement clause can be found, whether extraction is best-effort or authoritative, or whether results are cached.

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?

Front-loaded with the verb and object, which is good, but it is a single run-on sentence packing long parenthetical example lists. It also terminates mid-token at "comparison_ba", so the final field is never fully named — a real structural defect for an agent reading the definition.

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?

There is no output schema, so the description must convey return values; it does enumerate several extracted fields, but the list is cut off at "comparison_ba" and the remaining returned fields (e.g. the full comparison basis, any confidence or raw clause text) are never described, leaving the response shape partially unknown.

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%, documenting venue enum values, the .com/.us distinction, and the slug-vs-ticker input forms, so the baseline is 3. The description adds no parameter-level meaning beyond this; its detail about title fallback and precision formats concerns the output rather than the inputs.

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?

Uses a specific verb+resource ("Extract the settlement clause of a single ... market") and enumerates what is returned: source publisher, clock time + timezone, computation precision, comparison basis. The word "single" implicitly distinguishes it from a multi-market diff, but no sibling is named, so the contrast with nsi-bg__resolution_diff is left for the agent to infer.

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?

Usage is implied rather than stated: the agent can infer this is the per-market inspection tool, but there is no explicit when-to-use/when-not guidance and no pointer to resolution_diff for comparing two markets or to alternative tools. No prerequisites (e.g. that the market must exist upstream) are given.

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.