Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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.1/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 burden and delivers: it discloses that two audits are performed internally (implying double cost/latency), enumerates the compared fields, and defines the `equivalent` semantics including the confidence precondition and `differing_fields` on conflict. It omits error/failure behavior when a side cannot be parsed at all, and the final clause is cut off mid-word.

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 opening clause is well front-loaded and the return-value semantics are useful, but the second sentence is a run-on packing three distinct conditions, and the text terminates mid-word ('Polymarke'), leaving the key example incomplete. Valuable content, damaged structure.

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 explain returns, and it only partly does: `equivalent` true/false are defined, but the outcome when parse confidence is insufficient is left implicit and `differing_fields` is illustrated with a truncated example. For a two-parameter cross-venue diff tool this is adequate but leaves a real ambiguity an agent will hit on first use.

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 baseline is 3, but the description adds meaning the nested schema does not: the two objects must each carry exactly one market, and the venue values may be mixed across sides. That is real guidance beyond the per-object enum, though it does not explain accepted market identifier formats (slug vs. ticker per venue).

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 ('Field-by-field diff of TWO markets' settlement clauses') and bounds the inputs precisely: one market from each of `a` and `b`, any of Polymarket .com, Polymarket US, or Kalshi. It also names the internal mechanism (runs resolution_audit on both sides), which distinguishes it from the single-market sibling resolution_audit and from archive_compare.

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 cross-venue framing ('one from each of `a` and `b`', either can be any of three venues) makes the intended use case clear: comparing settlement terms across venues. It stops short of explicit routing guidance, e.g. it never says to use resolution_audit instead when only one market needs auditing, so the agent must infer the boundary.

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.