Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket perps order book

polymarket_perps_book_get
Read-onlyIdempotent

Fetches the Polymarket perpetuals order book for a given instrument ID, returning bid and ask price levels for market analysis.

Instructions

Get the Polymarket perps order book for one instrument. Requires instrumentId.

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": {
      "instrumentId": "<instrumentId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_perps_book_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoPrice levels per side: 10, 100, 500 or 1000. Default: 10.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
instrumentIdYesRequired. Perps instrument id from the instruments list.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no mention of snapshot vs streaming behavior, pagination, or typical staleness — leaving the behavioral burden entirely on structured fields.

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?

Two short sentences with the resource front-loaded and no filler. The second sentence is close to redundant with the schema's required-field marker, which is the only minor waste.

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?

For a simple single-instrument read with no output schema, the reader is left unsure what the book response contains (bids/asks, price levels, ordering) and how depth affects it. Annotations cover safety, but the return-shape gap keeps this at minimum-viable.

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%, including the depth enum with its default and the instrumentId pattern, so the baseline is 3. The description's only parameter remark, 'Requires instrumentId', repeats what the schema already marks as required and adds no new meaning.

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?

States a specific verb and resource ('Get the Polymarket perps order book') scoped to 'one instrument', which distinguishes it from the spot book sibling polymarket_books_get. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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?

The description offers no when-to-use or when-not-to-use guidance and names no alternative tool. 'Requires instrumentId' is a prerequisite restatement, not usage guidance, so the agent gets no help deciding between this and the perps tickers or klines tools.

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