Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__polymarket_arbitrage

Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a trending_scan of the top ~200 markets by weekly volume; pass event for the strongest per-event partition_check, or topic for a themed cross-event scan. event (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partit

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": {
      "topic": "Fed rate decision"
    },
    "name": "nj-mvc__polymarket_arbitrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventNoSingle-event mode (use this if you know the specific Polymarket event): event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k". Full Polymarket URLs also accepted.
topicNoCross-event mode (use this if you want to scan related events across the platform): a topic or seed question like "Fed rate decision" or "Strait of Hormuz traffic returns to normal". Tool searches Polymarket for related events and checks monotonicity across them.

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 at all, the description carries the full disclosure burden. It does add useful mechanics — walking child markets, checking date-axis/threshold-axis ordering, the ~200-market volume cap for the default scan — which is real behavioral context. However, it says nothing about cost/latency, read-only nature, rate limits, or what the response contains, and the final sentence is truncated mid-word ('computes the partit').

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 no-arg default is front-loaded, which is good, but the mode guidance is restated redundantly ('pass `event`' in the description and again as 'event (recommended for a specific market)'). The description also terminates mid-sentence, leaving an incomplete clause that wastes space and leaves the reader without the partition-sum explanation.

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?

For a two-optional-parameter tool with no annotations and no output schema, the mode guidance is sufficient to invoke it, but completeness gaps remain. An agent gets no sense of result shape, runtime cost, or how findings are reported, and the truncated ending removes part of the promised explanation.

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 both parameters are already fully documented in structured data, setting the baseline at 3. The description reinforces the mode semantics (event walks children and checks ordering; topic searches related events then checks monotonicity across them) but adds little beyond what the schema text already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Find arbitrage opportunities on Polymarket') and explains the mechanism (monotonicity violations + partition-sum checks). It clearly enumerates three distinct modes (trending_scan, event, topic), so an agent can tell the variants apart. It stops short of distinguishing this tool from Polymarket siblings like polymarket_edges or polymarket_edge_tracker.

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?

Mode selection is spelled out explicitly: no args → trending_scan of top ~200 markets by weekly volume; `event` → per-event partition_check; `topic` → themed cross-event scan. It even flags `event` as 'recommended for a specific market'. It does not say when to choose this over sibling Polymarket tools or when not to use it.

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.