Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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?

With no annotations at all, the description carries the full burden. It does disclose substantive behavior: the fee is never zero and is folded in rather than left to the caller, and the check is against live order-book depth rather than theoretical price. It never says whether the call is read-only, whether it requires auth, or what the response contains, and the truncation removes whatever came after the size_usd default.

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 first sentence front-loads the core capability, but it is freighted with a fleet issue number and a subreddit anecdote that consume space without helping an agent invoke the tool. The definition is also visibly truncated mid-clause ('size_usd (defa'), leaving an incomplete structure.

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?

With 4 parameters, full schema coverage, and no output schema, the agent still needs to know what a call returns and how to interpret the edge result; the description never gets there because it is cut off. The required-either/market-or-event rule is the most important missing piece and is at least stated, keeping this above a 2.

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 coverage is 100% and each parameter already carries a description covering side values, default buy_yes, basket auto-selection, and the 10-1,000,000 clamp on size_usd. The description restates the mode split between market and event but adds no syntax, URL-format, or validation meaning beyond the schema. Baseline 3 applies.

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 operation: comparing realizable vs theoretical edge against live CLOB order-book depth after folding in Polymarket's taker fee. The verb is somewhat nominal ('edge check') but the resource and computation are unambiguous. No sibling differentiation, though the supplied siblings are namespaced duplicates rather than genuine alternatives.

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 'REQUIRES one of market (single-market mode) or event (basket/partition mode)' and then describes what to pass in the single-market case, including side and size_usd defaults. This is real conditional guidance. It stops short of saying when to prefer this tool over any other analysis, and the text is cut off mid-sentence so the basket-mode instructions never arrive.

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.