Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket order books

polymarket_books_get
Read-onlyIdempotent

Fetch order books for up to 150 Polymarket outcome tokens in one request by providing token IDs, so you can inspect bids, asks, and price levels.

Instructions

Get the order books of up to 150 Polymarket outcome tokens in one request. Requires tokenIds.

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

Input Schema

NameRequiredDescriptionDefault
depthNoPrice levels returned per side, 1–200. Default: 20. Levels run from the best price outward.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
tokenIdsYesRequired. Outcome token ids, 1–150. Repeat the parameter or separate ids with commas. Token ids are the `tokenId` of a market outcome.
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.
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

B3.2/5.0
Behavior3/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 covered. The description adds the batch ceiling of 150 and that tokenIds is mandatory, but says nothing about snapshot timing, book ordering, partial-result behavior, or rate limits beyond what the schema states.

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 core capability front-loaded and no wasted clauses. The second sentence largely duplicates the schema's required-field marker, which is a small redundancy.

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 five-parameter tool with no output schema, the description covers the input requirement but does not describe the returned structure (e.g., bid/ask level arrays, default depth of 20 levels per side). Annotations carry the safety semantics, so this is adequate but leaves a real gap around return values.

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%, so all five parameters (depth, context, tokenIds, llm_model, conversation_id) are already well documented in the schema. The description's only added detail, the 150-token cap and the tokenIds requirement, merely restates schema constraints, 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 gives a specific verb and resource ('Get the order books') plus a scope quantifier ('up to 150 Polymarket outcome tokens in one request'), which is clear enough for an agent to identify the operation. It does not explicitly differentiate itself from siblings such as polymarket_perps_book_get or polymarket_prices_get, keeping it just below 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 guidance about when this tool should be chosen over alternatives (e.g., price endpoints or the perps book tool), nor any stated preconditions or exclusions. The only implied usage cue is the batch framing ('in one request').

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