Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get a Perps order book

get_perps_book
Read-onlyIdempotent

Retrieve a perpetual futures order book with best bid and ask levels first; specify instrument ID and depth, with prices in pUSD and quantities in base units.

Instructions

A Perps order book, best levels first. Prices in pUSD, quantities in base units.

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": {
      "instrument_id": "<instrument_id>"
    },
    "name": "get_perps_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoLevels per side.
instrument_idYesPerps instrument id, e.g. 1.

Output Schema

NameRequiredDescriptionDefault
asksYes
bidsYes
best_askNo
best_bidNo
sequenceNo
timestampNo
instrument_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that — that levels are returned best-first and that prices are in pUSD while quantities are in base units — but says nothing about snapshot vs. streaming behavior, staleness, or error handling for an unknown instrument id.

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?

Two short sentences with zero filler; the resource identification comes first and the unit conventions follow. Every clause carries information the agent would otherwise have to guess.

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 an output schema present and full parameter coverage in the schema, the description need not explain return values, and it correctly spends its words on the unit and ordering conventions that the schema does not cover. Minor gaps remain around data freshness and behavior for invalid instrument ids, but nothing essential to calling it correctly is missing.

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%: depth is documented as 'Levels per side' with an enum of 10/100/500/1000 and a default of 10, and instrument_id is documented as a perps instrument id. The description adds no parameter-specific meaning, so the baseline of 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 the specific resource ('A Perps order book') and its ordering, so an agent can tell it returns perps book data rather than candles, tickers, or trades. It does not explicitly contrast with the sibling get_order_books, which an agent might confuse it with, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite or exclusion, and no pointer to an alternative tool for related needs such as market listing or spot books. The agent must infer usage purely from the tool name and the 'Perps' qualifier.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools