Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it discloses internal behavior (runs resolution_audit on both sides), the compared fields, and the semantics of the `equivalent` and `differing_fields` return values. It omits cost/latency implications of two underlying audits and — due to truncation — the outcome when a side cannot be parsed with confidence.

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 comparison scope and input constraint are front-loaded in the first clause, followed by process and return semantics — a logical order with little filler. However, it is a single run-on sentence that is cut off mid-word ('Polymarke'), leaving the return-value explanation incomplete.

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?

With no output schema and no annotations, the description must fully define the return contract, and it only partly does: the `true` and `false` cases are explained, but the sentence is truncated before covering the third outcome (insufficient parse confidence) or the full shape of `differing_fields`. For a two-object nested-input comparison tool, an agent is left guessing about the indeterminate-result case.

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, and the description adds real meaning beyond the schema: each of `a` and `b` is one market from any of the three supported venues, and each is independently audited before comparison. It does not clarify whether the two markets must be the same underlying event.

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, with each side sourced from `a` and `b`. It explicitly scopes the venues (Polymarket .com, Polymarket US, Kalshi) and names the fields compared, which distinguishes it from the sibling nj-mvc__resolution_audit that it internally invokes.

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 the use case clear: comparing two markets' settlement terms across venues, and it names resolution_audit as the per-side building block, implicitly telling the agent to use this instead of auditing each side manually. It does not state exclusions, e.g. whether it works only for markets resolving on the same event or what to do for single-market audits.

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.