Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.6/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, and it does disclose real internals: it walks child markets, checks date-axis and threshold-axis ordering, computes partition sums, and scans the top ~200 markets by weekly volume. However, the text is truncated mid-word ("computes the partit"), so the behavioral account of event mode is literally incomplete, and nothing is said about result format or whether the scan is read-only/costly.

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 is well front-loaded and mode-by-mode structuring is sensible, but the final sentence is cut off mid-word, leaving a dangling fragment that both wastes space and costs information. Removing that defect, the rest is dense and largely free of filler.

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-mode scanning tool with no annotations and no output schema, the description should explain what an arbitrage result looks like and truncation aside, what event mode returns. The truncated tail and the total absence of return-value or cost/latency context leave real gaps, though the input-side guidance is solid.

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%, so baseline is 3; the description earns extra by adding mode semantics the schema does not state — that omitting all parameters yields a trending_scan over the top ~200 markets by weekly volume, and that event mode returns the strongest per-event partition_check. The slug/URL acceptance detail is duplicated from the schema rather than added.

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 opens with a specific verb and resource ("Find arbitrage opportunities on Polymarket") and names the detection techniques (monotonicity violations, partition-sum checks). It clearly separates the three invocation modes (no-arg trending_scan, event, topic). It does not distinguish itself from closely named siblings such as polymarket_edges or polymarket_edge_tracker, so it stops 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?

Usage is unusually explicit at the mode level: "Call with NO args for a `trending_scan`", "pass `event` for the strongest per-event partition_check", "or `topic` for a themed cross-event scan", plus "(recommended for a specific market)". What is missing is guidance against sibling arbitrage/edge tools — an agent cannot tell from this text why it would pick this over polymarket_edges.

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.