Skip to main content
Glama

Polymarket order quote

polymarket_quote
Read-only

Quote a Polymarket order before you place it: resolves the market and outcome token, walks the live order book for the expected fill (shares, average and worst price, slippage vs best and mid) and shows the platform fee and total cost. Read-only: places no order. Accepts a market slug, id, polymarket.com URL or a prediction_market_arbitrage id (polymarket:). Polymarket is close-only or blocked in the US and many other regions. Costs $0.005 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>"
    },
    "name": "polymarket_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNobuy (default) or sell
marketYesMarket slug, Gamma id, polymarket.com URL, or 'polymarket:<id>'
sharesNoFor a sell: shares to sell
outcomeNoOutcome to trade, e.g. 'Yes' or 'No' (default 'Yes')
amountUsdNoFor a buy: USD to spend
limitPriceNoOptional limit price between 0 and 1 (a multiple of the market's tick size)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: discloses the $0.005 USDC per-call cost, regional access restrictions (close-only or blocked in the US and many regions), that the call resolves the market/token itself, and that it walks the live book rather than returning a static price. These are exactly the operational facts an agent needs before spending money on a call.

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

Conciseness5/5

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

Front-loaded with the action and the returned data, then appends only two high-value operational notes (read-only, cost) and one risk note (regional restriction). No sentence is filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description fully describes the return payload (shares, average and worst price, slippage vs best and mid, platform fee, total cost), so an agent knows what it gets back. Combined with the cost and region warnings, nothing material is missing for a 6-parameter quote tool.

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 every parameter is already documented, and the description largely repeats the accepted market identifier formats rather than adding new constraints. It does hint at resolution of market and outcome token, but adds no syntax or default details beyond the schema, so 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?

Specific verb (quote) plus resource (Polymarket order) and an enumeration of what the quote contains: expected fill, average/worst price, slippage, fee, total cost. It clearly separates itself from generic odds tools by describing order-book walking, though it never names a sibling tool (e.g. swap_quote or prediction_market_odds) as the alternative.

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?

'Quote a Polymarket order before you place it' gives a clear usage moment, and 'Read-only: places no order' tells the agent this is a pre-trade check rather than execution. There is no explicit when-not or named alternative for a simple price lookup, which keeps it 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.

Resources