Skip to main content
Glama

NS Pros MCP Gateway

nobel__polymarket_fill_risk

Realizable-vs-theoretical edge check against live CLOB order-book depth, AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the direction that loses money). REQUIRES one of market (single-market mode) or event (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (defa

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": {
      "side": "buy_yes",
      "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
      "size_usd": 1000
    },
    "name": "nobel__polymarket_fill_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoSingle-market: buy_yes | sell_yes | buy_no | sell_no (default buy_yes). Basket: sell_yes | buy_yes (default auto, sell if partition sum > 1, buy if < 1).
eventNoBasket mode: event slug or full polymarket.com URL, checks every leg of the partition.
marketNoSingle-market mode: market slug or full polymarket.com URL.
size_usdNoSingle-market: USD to spend (buys) or target proceeds (sells). Basket: settlement notional, shares per leg, each paying $1 at resolution. Default 1000, clamp 10-1,000,000.

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?

No annotations are provided, so the description carries the full burden. It does disclose one genuinely non-obvious behavioral fact — that the taker fee is never zero and is already folded in, which guards against an optimistic read of the result. However, it says nothing about whether the tool is read-only, what a call costs, rate limits, or what the response contains, and the closing single-market guidance is cut off.

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 purpose is front-loaded, which is good, but the opening sentence spends considerable space on a fleet/Reddit anecdote justifying the fee handling rather than informing invocation. The text is also visibly truncated at 'size_usd (defa', leaving an incomplete sentence in a definition that is otherwise dense.

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 four-parameter analytic tool with no annotations and no output schema, the description covers mode requirements adequately but never indicates what the edge check returns or how to interpret it. Combined with the truncation, an agent knows how to call it but not fully what to expect back.

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 the schema already documents `side`, `event`, `market`, and `size_usd` including defaults and clamps; the baseline is therefore 3. The description repeats the default side and the default size without adding format or interpretation detail beyond what the schema states.

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 concrete operation: comparing realizable edge against theoretical edge using live CLOB order-book depth plus Polymarket's taker fee. It also separates single-market mode from basket/partition mode, which is more than a restatement of the name. It stops short of a crisp verb+resource phrasing, and the text is truncated mid-sentence, so the full scope is never quite closed.

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?

It gives an explicit precondition ('REQUIRES one of `market` ... or `event`') and explains the two operating modes, including that basket mode checks every leg of the partition. There are no stated exclusions or named alternatives, but the mode selection is spelled out well enough to act on.

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.