Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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?

With no annotations supplied, the description carries the full disclosure burden, and it does deliver genuinely useful traits: order-book depth is consulted, the taker fee is included rather than left to the caller, and the fee is 'never zero'. It does not state whether the call is read-only/side-effect free, how it behaves on thin or missing books, or what happens on failure — notable omissions for a tool with zero annotation coverage.

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 opening clause is dense and front-loaded, but the parenthetical about fleet #3446 and an r/PredictionsMarkets post spends a full sentence on sourcing anecdote that does not help an agent invoke the tool. The text is also truncated mid-sentence ('+ size_usd (defa'), leaving the structure visibly broken.

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 tool with 100% schema coverage but no output schema and no annotations, the description covers the essentials an agent needs to call it correctly: the two modes and their required parameter, the default side, and the fee/depth caveats. The main remaining gap is that with no output schema, nothing describes the shape of the result (realizable edge, slippage, fee breakdown), which the description would need to supply.

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 baseline is 3; the description largely restates the schema's mode split (market vs event, side, size_usd) rather than adding new meaning. It does add the framing that size_usd is a settlement notional in basket mode and a spend/target-proceeds in single-market mode, but that point is also present in the schema, and the sentence is cut off mid-word before reaching the size_usd detail.

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 first sentence states a specific computation — realizable-vs-theoretical edge checked against live CLOB order-book depth with the taker fee folded in — which is far more informative than the name 'fill_risk'. The sibling list shows the same tool replicated across source namespaces, so sibling differentiation is not the gap; the only weakness is that the description is truncated before it finishes defining the modes.

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 explicitly states the mode-selection precondition ('REQUIRES one of market (single-market mode) or event (basket/partition mode)'), which tells an agent which parameter unlocks which behavior. It frames the motivating context (avoiding an optimistic fill that omits fees) but never states when not to use it or what the alternative is, so it stops short of a 5.

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.