Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.8/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 behavioral burden and does much of it: it discloses that taker fees are non-zero and already folded in, that the check reads live order-book depth, and it explains the direction of the error being guarded against (optimistic results that lose money). It never states read-only/no-side-effect status or rate-limit behavior, which is the remaining gap for a zero-annotation tool.

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 core claim is front-loaded, but the definition is padded with a provenance digression ('fleet #3446: r/PredictionsMarkets flagged a "clean" fill...') that does not help an agent invoke the tool. It is also visibly truncated mid-parenthetical at 'size_usd (defa', leaving the single-market spec unfinished, which is a structural defect rather than economy.

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 and no annotations, so the description must cover everything; it explains inputs and the fee/depth logic but says nothing about the shape of the result (edge figures, fill price, warnings) the agent should expect. The truncation means even the input side is incomplete for a 4-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 earns above baseline by explaining the semantic difference between the two modes (single-market leg vs. partition basket) and the meaning of size on each side (USD to spend vs. target proceeds). The mode carve-out 'REQUIRES one of market or event' adds a constraint the schema does not express as a hard requirement.

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 concrete operation: comparing realizable versus theoretical edge against live CLOB order-book depth while folding in Polymarket's taker fee. That is a specific verb-plus-resource statement an agent can act on. It stops short of a 5 only because the opening phrasing is dense and the sentence trails off before finishing the single-market specification.

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 mode-selection rule: 'REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode)', so the agent knows which parameter selects which behavior. It does not say when a caller should skip this tool entirely (e.g., pre-trade vs. post-trade, or when order-book data is unavailable), so it falls short of full when/when-not guidance.

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.