Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does real work: it discloses that the taker fee is non-zero and is folded into the result rather than left to the caller, and that pricing is checked against live order-book depth rather than a mid-price. The anecdote about an omitted fee producing an optimistic fill is useful framing for why the number differs from a naive calculation. It loses a point because the truncation leaves the return shape and any rate-limit or auth behavior unstated.

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 precondition and mode split are front-loaded, which is good structure. But the parenthetical about 'fleet #3446' and a Reddit thread is provenance noise that costs tokens without changing how an agent calls the tool, and the text terminates mid-sentence, leaving the definition visibly incomplete.

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?

For a 4-parameter tool with no annotations and no output schema, the description covers the inputs and the fee/depth behavior reasonably well. What it omits is what the caller actually receives — edge figures, slippage, or a pass/fail signal — and the truncation means an agent cannot confirm the result contract before invoking.

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 `side`, `market`, `event`, and `size_usd` including defaults and the 10-1,000,000 clamp. The description restates the same defaults and adds only the basket interpretation of `size_usd` as settlement notional. That is marginal added meaning over structured data, so the 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?

The description names a specific operation: comparing realizable edge against theoretical edge using live CLOB order-book depth plus Polymarket's taker fee. That is a concrete verb+resource, not 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 the output is never stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a hard precondition ('REQUIRES one of `market` ... or `event`') and explains the two operating modes, which is genuine routing guidance between modes. However, it never says when an agent should reach for this tool versus other market-data tools, and no alternative is named. Mode selection is covered; tool selection is not.

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.