Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavior burden. It does disclose meaningful internals: walking child markets, checking date-axis and threshold-axis ordering, and computing partition sums. However, it is cut off mid-word ("computes the partit"), says nothing about the read-only nature of the tool, rate limits, or what the response contains, leaving notable gaps.

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 most important information (no-arg trending scan, then the two modes) is front-loaded, which is good. But the text is verbose with repetitive restatement of the event mode and, critically, is truncated mid-sentence, leaving the structure visibly broken.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no annotations and no output schema, so the description must carry both behavioral and return-value context, and it does neither fully. It ends mid-sentence, leaving the partition-sum explanation incomplete and never indicating what results look like or how large a scan is. For a two-mode analysis tool this is under-specified.

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 fully documented in the schema, including slug formats and URL acceptance. The description reinforces the mode distinction but adds little syntactic or behavioral detail beyond what the schema states, which is the expected baseline of 3.

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 states a specific verb and resource: find arbitrage opportunities on Polymarket via monotonicity violations and partition-sum checks. That is far more informative than a restatement of the name. It does not differentiate itself from close siblings such as polymarket_edges or polymarket_edge_tracker, so it falls short of a 5.

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 gives explicit mode-selection guidance: no args for a trending scan of the top ~200 markets by weekly volume, event for a single-event partition check, and topic for a cross-event scan. It also recommends event when a specific market is known. It never names a sibling alternative or a when-not-to-use condition, which keeps it out of 5 territory.

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.