Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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 are supplied, so the description carries the full behavioral burden. It does add genuine value by disclosing a fallback rule (resolve the time range from the market TITLE when the clause says "the time range specified in the title," e.g. the 15-minute Chainlink TWAP family) and the normalization of precision strings, but it says nothing about failure modes, unsupported markets, or the response shape, and it terminates mid-token at "comparison_ba".

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 lead sentence correctly front-loads the verb and resource, but the body collapses into one dense run-on enumerating extracted fields with nested parentheticals and slash-separated alternatives. It is informative rather than padded, yet the trailing truncation at "comparison_ba" shows the sentence outran its useful length.

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?

For a two-parameter extraction tool with a fully documented schema, the key remaining gap is the return contract: no output schema exists, and the field enumeration breaks off mid-word, leaving comparison_basis and any other returned clause attributes undefined. An agent knows what to send but only partially what it will get back.

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%: the enum options, the venue distinction between polymarket.com and the CFTC-regulated polymarket.us, and the ticker-vs-slug accepted forms are all in the schema. The description restates the venues without adding format rules for the truncated comparison field or any constraint beyond what the schema already gives, so baseline 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," then enumerates the components returned (source, clock time/timezone, precision). It is clear what the tool does, though the venue coverage (Polymarket/Kalshi) reads oddly against a name prefixed 'nobel' and no explicit sibling differentiation is offered.

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 the scope statement 'a single market' and the example inputs, so an agent can infer one market per call. However there is no explicit when-to-use, no when-not, and no pointer to an alternative for multi-market or batch resolution lookups.

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.