Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_tokens_prices

Fetch public Polymarket CLOB buy and sell prices for up to 25 token IDs, with no wallet or account authentication required. Omit side to get both.

Instructions

Get Polymarket token prices. Returns public CLOB buy and sell prices for up to 25 Polymarket token ids. The side enum accepts buy and sell; when omitted, both sides are returned. This does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.

Input 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: +{
+  "side": {
+    "type": "string"
+  },
+  "token_ids": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
    • addedInput schema / properties / body / required
      Added value: +[
+  "token_ids"
+]
  2. Addedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a useful behavioral fact beyond the schema: 'public CLOB buy and sell prices' and that no Polymarket user token, wallet signature, cookies, or account auth is required. However, it says nothing about rate limits, failure modes, or how the price data is sourced or refreshed.

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?

Three tight sentences, front-loaded with the core purpose, followed by scope and auth details. No padding or redundancy; each sentence carries distinct information.

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 batch read tool with no annotations and no output schema, the description covers purpose, batching, side semantics, and auth requirements adequately. It needn't describe return values, but the absence of any note on pricing semantics or ordering is a minor gap.

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?

Schema coverage is nominally 100%, but the schema leaves `side` as a bare string and `token_ids` undocumented. The description compensates by explaining the `side` enum semantics ('buy'/'sell'; omitted returns both) and the 25-id batch cap, adding meaning the structured fields do not carry.

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 Polymarket token prices) and clarifies scope: public CLOB buy/sell prices for up to 25 token ids. The batch nature ('up to 25 token ids') distinguishes it from the singular sibling polymarket_token_price, but no sibling is named explicitly, so it stops short of full differentiation.

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 never states when to use this tool versus alternatives such as polymarket_token_price (single), polymarket_tokens_spreads, or polymarket_tokens_orderbooks. Usage is only implied by the batch scope; no exclusions or preconditions are given.

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