Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.9/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 behavioral burden. It discloses real internal behavior ('walks child markets, checks date-axis / threshold-axis ordering'), which is valuable, but it says nothing about cost, latency, rate limits, or whether the tool is strictly read-only, and the text is cut off mid-word ('computes the partit'), so part of the behavioral disclosure is simply missing.

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 structure is good — default behavior first, then the alternative modes — but the text is dense with unexplained jargon and, as supplied, ends mid-sentence in the middle of the most technical explanation. An incomplete trailing clause is a real defect in a definition this technical.

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-param, zero-annotation, no-output-schema tool, the definition covers the mode selection well but leaves gaps: the return shape of a scan is never described, the truncated partition-sum explanation is unresolved, and nothing tells an agent how large or costly a trending scan of ~200 markets is. Adequate, not complete.

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 already 100%, so the schema documents both `event` and `topic` including slug examples. The description adds modest extra meaning (that `event` is 'recommended for a specific market', that the tool 'walks child markets' in that mode), but it largely restates the schema's own mode descriptions rather than adding new semantics.

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?

The opening sentence names a specific verb and resource ('Find arbitrage opportunities on Polymarket') and even names the detection methods (monotonicity violations, partition-sum checks). An agent immediately knows this is an arbitrage-detection tool over prediction markets, not a generic market lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly maps three calling modes: no args for `trending_scan` of the top ~200 markets by weekly volume, `event` for a per-event partition_check (marked 'recommended for a specific market'), and `topic` for a themed cross-event scan. The when-to-use condition for each mode is stated, not left to inference.

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.