Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_tokens_orderbooks

Get Polymarket token order-book depth for up to 25 token IDs using public CLOB data without authentication.

Instructions

Get Polymarket token order books. Returns public CLOB order-book depth for up to 25 Polymarket token ids. This uses credential-free public CLOB market-data JSON and does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesToken ids request body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / body / properties
      Added value: +{
+  "token_ids": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
    • addedInput schema / properties / body / required
      Added value: +[
+  "token_ids"
+]
  2. Addedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that this is a credential-free, public CLOB market-data call requiring no user token, wallet signature, cookies, or personal authentication. It does not mention response structure or rate limits, but for a read-only public data endpoint the disclosure is solid.

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 sentences with no filler. The primary action, the return value, the batch limit, and the authentication-free nature are all front-loaded and clearly expressed.

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?

The tool has a simple one-parameter body, no output schema, and no annotations, but the description covers the essential invocation details: what is returned, the max batch size, and the lack of authentication requirements. It could be more complete by describing the output shape, but it is sufficient for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only defines token_ids as an array of strings within a body object, while the description adds a meaningful constraint: 'up to 25 Polymarket token ids.' This gives the agent a limit not present in the schema, going beyond the baseline coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get Polymarket token order books.' It adds concrete scope by stating it returns 'public CLOB order-book depth for up to 25 Polymarket token ids,' which clearly separates it from the singular sibling polymarket_token_orderbook by indicating this is the batch variant.

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?

The description gives clear usage context: use this tool when you need order-book depth for multiple Polymarket token ids (up to 25). It does not explicitly name alternatives such as polymarket_token_orderbook for single-token requests, so it misses the top score, but the batch-scenario framing is clear enough.

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