Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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 full burden. It does disclose genuinely non-obvious behavior: the fallback to the market TITLE when the clause references "the time range specified in the title," with the 15-minute Chainlink TWAP family as a concrete example. It does not cover error behavior, unsupported markets, rate limits, or the truncated output-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.

Conciseness3/5

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

The core purpose is front-loaded in the first clause, which is good. But the body is a single sprawling sentence with deeply nested parentheticals and multiple example styles, and it terminates mid-word, which reads as an unfinished dump rather than structured guidance.

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 semantics; it does so partially by naming extracted fields (source, clock time + timezone, precision, comparison_basis) before being truncated. Missing are the completion of that field list and any statement of failure modes for unsupported venues or malformed slugs.

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 schema itself explains the polymarket vs polymarket-us distinction and the slug/URL/ticker forms. The description adds no parameter meaning beyond that, 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?

States a specific verb and resource: "Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market." The "single market" qualifier implicitly separates it from a comparison-style sibling, but no sibling is named and the trailing clause is cut off mid-token ("comparison_ba"), so the full scope is never fully stated.

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 by "single" market and by the venue enumeration, suggesting this is the per-market lookup. However, there is no explicit when-to-use/when-not framing and no named alternative (e.g. resolution_diff) for multi-market comparisons, leaving the agent to infer routing.

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.