Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.2/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 disclosure burden, and it does add one genuinely useful behavioral detail: the parser falls back to the market TITLE when the clause says 'the time range specified in the title' (Polymarket's 15-minute Chainlink TWAP family). That is real parsing behavior an agent could not get from the schema. However, it never states that this is a read-only extraction, says nothing about failure modes when a clause is missing or ambiguous, and the truncation hides whatever came after 'comparison_ba', leaving the output behavior underspecified.

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 entire definition is one run-on sentence held together by nested parentheses and slash-separated examples ('1-minute candle close' vs '60-second trailing average' vs 'twap_60s_lookback'/'twap_30s_lookback' vs 'election outcome'). The core purpose is front-loaded, which helps, but the enumeration is exhausting and the text is truncated mid-word, so the structure fails at its most important job - telling the agent what the tool returns.

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 the return shape, and it does partially: source publisher, clock time plus timezone, computation precision, comparison basis. That is meaningful coverage for a clause-parsing tool whose complexity is high. But the cut-off leaves the field list incomplete and no statement about behavior when the clause cannot be parsed, which for a two-venue extraction tool is a material gap.

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 carry detailed descriptions upstream, including the polymarket-us enum nuance and the Kalshi ticker-vs-event-ticker fallback, so the baseline of 3 applies. The description reinforces the venue scope but adds no new semantics about accepted slug formats, URL handling, or ticker normalization beyond what the schema already states. Nothing is lost, but nothing is added.

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 states a specific verb and resource: 'Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market.' That scoping - one market, these venues, this artifact - distinguishes it from contextual siblings like resolution_diff, though the sibling differentiation is only implicit. The sentence then degenerates into a dense enumeration and is cut off mid-token ('comparison_ba'), so the full scope of what is extracted is never cleanly 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 only implied: 'a single ... market' suggests a per-market lookup versus a batch or diff tool, and the mention of falling back to the market TITLE suggests when clause-based extraction alone is insufficient. There is no explicit 'use this when / do not use this when', no mention of what to call instead for multi-market comparisons, and no statement of prerequisites. An agent can infer the context but is not routed.

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.