Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_token_orderbook

Retrieve a Polymarket outcome token's order book using its token_id to inspect bids, asks, last trade price, tick size, minimum order size, condition id, and timestamp.

Instructions

Get Polymarket token order book. Returns the order book for one Polymarket outcome token, identified by the required token_id. The book has bids and asks as price and size pairs, the last trade price, tick size, minimum order size, condition id and a timestamp. Prices and sizes are numbers.

Input Schema

NameRequiredDescriptionDefault
token_idYesPolymarket CLOB token id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does disclose the returned structure in detail: bids/asks as price-size pairs, last trade price, tick size, minimum order size, condition id, and format notes that prices/sizes are numeric. It omits any note on auth, rate limits, or empty-book behavior, which keeps it from a 5.

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 purpose sentence, then a compact return-shape enumeration. Every sentence contributes; only the nested path notation ('the `book` has') is slightly raw but functional.

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?

For a single-parameter read tool with no output schema, the description supplies the missing return-value detail an agent needs to interpret the response. Complete on the call path; only empty/edge-case behavior and any auth expectations are unaddressed.

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 the schema already documents token_id. The description restates it as required and adds the framing 'one Polymarket outcome token' and 'CLOB token id', which is marginal semantic value beyond the schema - baseline 3.

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+resource (get/order book) and scopes it to 'one Polymarket outcome token', which implicitly separates it from the sibling batch tool polymarket_tokens_orderbooks. It never names that sibling explicitly, so sibling differentiation is inferred 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 Guidelines3/5

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

The description establishes that a single token is required but gives no when-to-use, when-not-to-use, or alternative routing (e.g. vs polymarket_token_midpoint, polymarket_token_spread, or the batched orderbooks tool). Usage is only implied by the required token_id.

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