Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_tokens_prices

Retrieve Polymarket token prices using public CLOB buy/sell quotes for up to 25 token IDs. No login or wallet needed; pass token IDs and optional side to return clean market data.

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

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does substantial work: it explicitly states the endpoint is credential-free public CLOB market data and needs no user token, wallet signature, cookies, or auth. It also discloses the batch cap and side default. It stops short of error behavior and response format, but the most consequential operational traits are covered.

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?

Three sentences, no filler; the core verb/resource is front-loaded, followed by limit, side behavior, and auth. Every sentence adds information needed for correct selection and invocation.

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 one-body-parameter public read endpoint, the description covers inputs, auth, limit, and side default. The only real gap is the absence of an output schema and no prose about the exact response shape or behavior on invalid/over-limit ids, but this does not block correct invocation.

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 types `side` as a string and labels `body` as 'Token ids request body', so the description adds real meaning: side accepts buy/sell, omission returns both sides, and token_ids is bounded at 25. This exceeds the baseline for 100% schema 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?

Description opens with a specific verb and resource ('Get Polymarket token prices') and immediately narrows scope: public CLOB buy/sell prices for up to 25 token ids. The batch size and side semantics distinguish it from sibling orderbook, midpoint, and single-price tools even though no sibling is named.

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 makes the intended use clear (batch current buy/sell prices for up to 25 token ids), and the optional side behavior is stated. However, it never tells the agent when to prefer this over sibling price/orderbook/midpoint tools or which alternatives to choose, so routing is left to inference.

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