Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load, and it does disclose meaningful behavior: the internal resolution_audit call on both sides, the five fields compared (source, settle time, precision, comparison_basis, evidence standard), and the exact rule for `equivalent` = "true" (both sides parsed with sufficient confidence AND no conflicts). It does not say what is returned when parse confidence is insufficient — the text is truncated exactly at the case that would explain that — which is a real gap for a comparison tool with zero annotation coverage.

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?

Front-loaded with the core purpose, and no sentence is filler. However, it is a single dense run-on with deeply nested parentheticals, and the final clause is cut off mid-word ('for a Polymarke'), leaving the worked example of `differing_fields` 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, the description must explain return values, and it does describe `equivalent` and `differing_fields` in useful detail. But for a nested-object comparison tool the enumeration of possible outcomes is incomplete — the low-confidence case and the full `differing_fields` example are missing due to truncation — so an agent cannot fully predict the response shape.

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% and the nested objects already document `venue` and `market`, so baseline is 3. The description adds genuine meaning beyond the schema by clarifying that exactly one market comes from each of `a` and `b` and that the two sides may be the same or different venues, which constrains how the pair should be chosen.

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 pins scope precisely: one market from each of `a` and `b`, any of Polymarket, Polymarket US, or Kalshi. An agent can tell this apart from a single-market audit 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 Guidelines4/5

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

Gives clear context for use — comparing settlement clauses across two venues to test equivalence — and notes it internally runs resolution_audit on both sides, which implicitly routes single-market auditing elsewhere. It stops short of an explicit 'use this instead of X when...' exclusion, so it is not a 5.

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.