Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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, the description carries the whole burden, and it does disclose a meaningful behavioral trait: the taker fee is never zero and is already included rather than left to the caller, which prevents an over-optimistic read of results. It never says whether this is a pure calculation or whether any order/commitment is made, and gives no return-shape or latency expectations. That ambiguity matters most for a trading-adjacent tool with zero annotation coverage, so it lands at adequate rather than strong.

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?

Purpose and mode requirement are front-loaded, which is good, but the description is visibly truncated mid-word and spends a long parenthetical on a 'fleet #3446 / r/PredictionsMarkets' anecdote. The anecdote does justify the fee handling, but it is verbose relative to its informational payoff. Structure is acceptable, polish is not.

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?

There is no output schema, so the description should say what comes back (realizable edge, slippage, fee breakdown, per-leg results in basket mode) and it does not. Mode inputs and the fee treatment are covered, and the schema handles parameters fully. For a computational check whose entire value is its output, the missing return description is a real gap.

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 defines `side` enums, default `buy_yes`, and the `size_usd` default and clamp. The description only restates the mode-to-parameter mapping (market vs event, side + size for single-market). Baseline 3 is appropriate — it adds routing meaning but no syntax 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?

The description states a specific analysis: comparing realizable vs theoretical edge against live CLOB order-book depth with Polymarket's taker fee folded in. It also names the two operating modes (single-market via `market`, basket via `event`), so an agent can tell what the tool computes and how it is scoped. It stops short of a crisp one-line summary — the core purpose is embedded in a long clause with a community-forum citation.

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?

Explicit prerequisite is given: 'REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode)', plus a per-mode description of what each expects. This is real when-to-use guidance for mode selection. It does not state when to skip this tool entirely (e.g. a plain quote lookup), and the sentence is cut off mid-thought ('size_usd (defa'), leaving the size contract elsewhere.

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.