Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the mechanism (walks child markets, checks date-axis/threshold-axis ordering, computes partition sums) and the scan scope (~200 markets by weekly volume), which is genuine value. However, the text is truncated mid-word ('computes the partit'), so the core partition-sum logic and what an 'opportunity' actually looks like are never finished, and there is no statement about rate limits, read-only safety, or cost of a scan.

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 sentence is well front-loaded with purpose followed by mode selection, which is good structure. But the final sentence is cut off mid-word, leaving an incomplete and unusable fragment that wastes space and breaks the flow of an otherwise tight definition.

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 should convey what a caller gets back. It explains the modes and the detection axes but never describes the return shape (opportunities, spreads, confidence) or how many results to expect. Combined with the truncated final sentence, the definition is adequate but leaves a meaningful gap for a no-arg scan tool.

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 `event` and `topic` are already documented with format examples and URL acceptance. The description reinforces the mode semantics and gives additional slug examples, but adds little meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Find arbitrage opportunities on Polymarket,' and names the detection method (monotonicity violations + partition-sum checks). An agent immediately knows this is an analysis/scan tool rather than a raw market-data fetch.

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 each mode to a condition: no args for a trending_scan over the top ~200 markets by weekly volume, `event` for a single-event partition check (explicitly 'recommended for a specific market'), and `topic` for a themed cross-event scan. All three invocation paths and their selection criteria are spelled out.

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.