Skip to main content
Glama

NS Pros MCP Gateway

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

B3.3/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 add genuinely useful behavior that structured fields cannot convey: the taker fee is never zero and is already included rather than left for the caller to add, plus a warning that clean-looking fills can be optimistic. However it never states what the call returns, whether it is read-only or consumes quotes, or any latency/rate characteristics, and the truncation prevents disclosure of the size_usd handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and mode requirement are reasonably front-loaded, but an entire parenthetical citing an internal ticket and a subreddit report ("fleet #3446: r/PredictionsMarkets flagged a 'clean' fill...") is provenance noise that costs tokens without changing how the agent calls the tool. Worst of all, the description terminates mid-sentence, leaving the size_usd contract incomplete.

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?

There is no output schema, so the description is the only place an agent could learn what a fill-risk result looks like, and it never says. Combined with the truncated tail, an agent knows the tool's intent and its mode gate but not its return shape or the full size_usd semantics — a real gap for a 4-parameter analytical 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% and the schema already documents side enums, mode selection, size_usd defaults and clamping, so the baseline is 3. The description reinforces the default side (buy_yes) and the required-one-of constraint but adds no syntax or format detail beyond the schema, and its size_usd explanation is truncated exactly where it would have added value.

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 specific operation: a realizable-vs-theoretical edge check run against live CLOB order-book depth, with Polymarket's taker fee folded in. That is a concrete verb-plus-resource statement rather than a restatement of the name. It stops short of 5 because the sentence is cut off mid-clause ("+ size_usd (defa"), so the full scope of what is computed is never spelled out.

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 states an explicit precondition ("REQUIRES one of `market` ... or `event`") and then maps each mode to a use case: single-market vs basket/partition. That gives an agent clear routing between two invocation shapes. No exclusion or when-not-to-use guidance is given, and there is no mention of any 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.