Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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 load and does real work: it discloses that two resolution_audit calls happen underneath, that comparison is gated on parse confidence, and that `equivalent` is true only when both sides parsed confidently AND no field conflicts exist, with `differing_fields` naming the conflicts. Gaps remain — no mention of what happens when a side cannot be parsed at all, no cost/latency warning despite two upstream calls, and the text is cut off mid-sentence.

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 comparison scope and the return-value semantics are front-loaded and useful, but the description ends mid-word ('for a Polymarke'), leaving a trailing fragment that conveys nothing and signals an unfinished spec. The dense field enumeration is efficient, yet the truncation costs real clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter comparison tool with no output schema and no annotations, the description supplies the key missing context: what is compared, what the boolean means, and what the conflict list holds. It is only incomplete because the final clause is truncated, so the behavior when one side cannot be parsed with confidence is left ambiguous.

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 nested venue/market objects are documented, so the schema already does the heavy lifting. The description adds that either side may be Polymarket .com, Polymarket US, or Kalshi, which restates the enum rather than extending it, and gives no guidance on market identifier formatting beyond the schema's example.

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?

States a specific verb and resource — a field-by-field diff of two markets' settlement clauses — and enumerates the exact compared fields (source, settle time, precision, comparison_basis, evidence standard). It implicitly separates itself from the sibling resolution_audit by describing that tool as the per-side primitive this one invokes on both sides.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes clear this is the tool for comparing TWO markets and that each of `a` and `b` supplies one market; it also names resolution_audit as the single-market alternative it wraps. It does not state when a plain single-side audit is preferable or when comparison is not meaningful, so it stops short of explicit exclusions.

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.