Skip to main content
Glama

Polymarket orderbook

polymarket_orderbook
Read-onlyIdempotent

Live Polymarket CLOB L2 orderbook depth & slippage simulator: pass tokenId or slug (defaults to top active market) for best bid/ask, spread bps, mid probability, OBI, exact buy/sell slippage, and resting walls. $0.002 per call over x402 or X-API-Key. Not advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "polymarket_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOptional Polymarket market slug.
sizesNoComma-separated USD sizes (default 100,500,2500).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
tokenIdNoOptional Polymarket CLOB outcome token ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the safety bar is low. The description adds genuinely useful non-schema context: a per-call cost ($0.002) and the two payment/auth routes (x402 or X-API-Key), which an agent must know before invoking. It does not cover rate limits, failure modes, or depth limits, so it is solid but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource and scope, then parameters, then output fields and pricing in a single tight block with no filler. Densely packed jargon (OBI, bps, L2) is left unexpanded, which costs a bit of immediate clarity.

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?

With no output schema, the description correctly compensates by enumerating the return fields, and it discloses cost and auth. What remains thin is invocation edge cases (invalid tokenId, empty book) and whether the slippage simulation requires the sizes parameter, but for a 4-param read-only tool it is largely complete.

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 coverage is 100%, so tokenId, slug, sizes, and payment are already documented in the schema, which sets the baseline at 3. The one real addition is the stated fallback behavior when neither tokenId nor slug is given, plus the default size ladder implication via the schema; 'sizes' and 'payment' get no elaboration in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource ('Live Polymarket CLOB L2 orderbook depth & slippage simulator') and enumerates the outputs (best bid/ask, spread bps, mid probability, OBI, slippage, resting walls). The Polymarket/CLOB scoping clearly separates it from sibling orderbook tools such as kalshi_orderbook and hl_orderbook_edge.

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?

Gives clear invocation context: pass tokenId or slug, and if neither is supplied it defaults to the top active market. It does not state when to prefer this over a sibling orderbook tool or any exclusions, so it stops 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.

Resources