Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does valuable work by disclosing the return contract: `equivalent` is "true" only when both sides parsed with enough confidence AND no fields conflict, and "false" when a specific conflict exists with `differing_fields` naming them. However, the explanation of the "false/insufficient confidence" branch is cut off mid-word, and nothing is said about cost (two audits run per call), missing markets, or failure behavior.

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 field list is efficient. But the description terminates mid-sentence at 'for a Polymarke', leaving a dangling fragment that undercuts the otherwise dense structure and visibly signals missing content.

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 return values, and it does so for the `equivalent` and `differing_fields` fields. The critical remaining case — what is returned when a side cannot be parsed confidently, i.e. the third state between true and false — is exactly where the text is truncated, leaving the contract incomplete for a tool that itself fans out to two audits.

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%, so the two nested parameters and their venue enums are already documented structurally. The description adds only the mild clarification that the two sides are symmetric (either `a` or `b` can be any of the three venues) rather than a reference-vs-candidate pair; it adds no detail on market identifier formats beyond what the schema example shows.

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?

Names a specific verb and resource: a field-by-field diff of two markets' settlement clauses, where each side may come from Polymarket .com, Polymarket US, or Kalshi. It also states the internal mechanism (runs resolution_audit on both sides) and the fields compared (source, settle time, precision, comparison_basis, evidence standard), so an agent knows exactly what this produces.

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 'two markets, one from each of a and b' framing, and the venue constraint is stated. But there is no explicit when-to-use versus when-not, no mention of when to call resolution_audit directly instead, and no guidance for the case where a side cannot be resolved confidently.

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.