Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__resolution_diff

Field-by-field diff of TWO markets' settlement clauses (one from each of a and b; either can be Polymarket .com, Polymarket US, or Kalshi), runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns equivalent: "true" only when both sides parsed with enough confidence to compare AND no field conflicts; "false" when a specific conflict was found (differing_fields names which, e.g. ["source","settle_time"] for a Polymarke

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": {
      "a": {
        "venue": "polymarket",
        "market": "bitcoin-above-70k-on-september-13-2026"
      },
      "b": {
        "venue": "kalshi",
        "market": "KXBTCD-26SEP1317"
      }
    },
    "name": "nsf-awards__resolution_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst market to compare.
bYesSecond market to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it names the compared fields, explains that resolution_audit runs on both sides, and defines equivalent as true only when both sides parse with enough confidence and no conflicts exist. It also notes that false is returned for a specific conflict and that differing_fields identifies the conflict, though it omits error behavior and the ending is truncated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is front-loaded with the core purpose and then explains return semantics, with little wasted wording. However, the first sentence is a dense run-on and the description ends with an incomplete clause, which slightly reduces clarity.

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?

No output schema exists, so the description must explain return values. It does explain equivalent and differing_fields at a high level, but the truncated ending and the absence of details about output shape, insufficient-confidence behavior, or error cases leave meaningful gaps for a diff tool with nested inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the a and b parameters. The description adds meaningful context beyond the schema by clarifying that one market comes from each of a and b and that either side can be Polymarket .com, Polymarket US, or Kalshi, enabling mixed-venue comparisons. It does not explain the expected market identifier format beyond the schema examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: a field-by-field diff of two markets' settlement clauses. It distinguishes itself from the single-market audit by specifying TWO markets and noting that resolution_audit runs on both sides, so an agent can identify its role without opening the schema.

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?

The description implies the tool is for comparing two markets' settlement terms, but it never explicitly says when to use this instead of resolution_audit or other sibling tools. It also gives no exclusions or prerequisites, leaving usage guidance to inference.

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.