Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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.6/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 burden. It does disclose a non-obvious behavioral trait — that Polymarket's taker fee is always non-zero and is folded in rather than left to the caller — and that pricing comes from live CLOB depth rather than mid/last. However, it never says whether the call is read-only analysis or places anything, gives no rate-limit/auth/reversibility context, and the text truncates before finishing the constraint set.

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 core requirement and mode split are reasonably front-loaded, but the definition is cluttered with an anecdotal citation ('fleet #3446: r/PredictionsMarkets flagged a "clean" fill...') and heavy parenthetical jargon, and it cuts off mid-token with '(defa'. Under-specification from truncation, not verbosity alone, costs it here.

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

Completeness4/5

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

For a 4-parameter, no-annotation, no-output-schema tool, the description covers the essential elements: what is measured, both modes, the fee treatment, and basket settlement semantics ('shares per leg, each paying $1 at resolution'). The gap is that it never describes the shape of the result (edge figure, slippage, pass/fail) and the text is truncated.

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 all four parameters including enum values and defaults — baseline 3. The description adds the mode-to-parameter mapping (market => single-market, event => basket) and reiterates the side default, but the truncated tail means size_usd semantics are not elaborated beyond the schema.

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?

States a specific verb+resource: a 'realizable-vs-theoretical edge check' computed against live CLOB order-book depth with the taker fee folded in. The two operating modes (single-market vs basket/partition) are named, so the agent knows what the tool produces. It stops short of 5 because the prose is dense and truncated mid-sentence, and the sibling names are provider-prefixed duplicates that give no real differentiation signal.

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?

Explicitly states the selection rule: 'REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode)', then splits guidance by mode with defaults per mode. That is clear when-to-use-by-mode guidance. It lacks any exclusion ('don't use this when you only want last price') or named alternative tool.

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.