Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.7/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 it does disclose a non-obvious behavioral trait: the Polymarket taker fee is never zero and is folded in rather than left to the caller, with a cited real-world failure of a fill that omitted it. That is genuinely useful behavioral context beyond structured fields. It does not state read-only status, latency, or rate behavior, and the cited 'fleet #3446' anecdote is more provenance than guidance.

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 scoping constraint and fee disclosure are front-loaded, but the sentence is overloaded with a long parenthetical citing ticket #3446 and a Reddit thread, which is provenance rather than operating information. More damaging, the text is truncated mid-token at 'size_usd (defa', so the final and arguably most important clause never lands.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 must explain what the check returns and how to read the realizable-vs-theoretical result, and it never gets there because it truncates. Basket mode, which the description itself declares mandatory as an alternative to `market`, is only covered by the input schema. For a risk-evaluation tool whose output is a judgment, this leaves a significant gap.

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 coverage is 100%, so the baseline is 3, but the description adds a constraint the schema does not encode: despite `required: []`, one of `market` or `event` must be supplied, and the choice selects the operating mode. It also reiterates `side` defaults and `size_usd`, which duplicates the schema. The added mutual-exclusivity rule is the real value here.

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 opening clause names a specific computation: realizable-vs-theoretical edge measured against live CLOB order-book depth, plus the taker fee folded into the result. That is far more precise than a restatement of the name, and it distinguishes this from a naive theoretical-edge calculation. Sibling names are all identical replicas across namespaces, so no sibling differentiation is possible or needed.

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 the hard precondition clearly: one of `market` (single-market mode) or `event` (basket/partition mode) is REQUIRED, then walks through what to pass in single-market mode. That is explicit mode-selection guidance an agent can act on. The basket-mode half of the sentence is cut off mid-word, so the when-to-use story for `event` is left to the schema.

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.