Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_tokens_midpoints

Fetch public CLOB midpoints for up to 25 Polymarket token IDs without user tokens, wallet signatures, cookies, or account authentication.

Instructions

Get Polymarket token midpoints. Returns public CLOB midpoints 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 provided, the description carries the full burden. It discloses that the operation is credential-free and uses public CLOB data, implying read-only behavior. It also adds the 25-token limit. It does not describe pagination or error handling, but for a simple read it is sufficient.

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 with no waste. The action and resource are front-loaded, and the auth/limit details are included succinctly. Every sentence earns its place.

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 simple batch read tool with one parameter and no output schema, the description covers the key aspects: what it returns, the limit, and authentication requirements. It could specify the return format, but that is a minor gap given the tool's simplicity.

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 100% but the schema description for 'token_ids' is minimal ('Token ids request body'). The description adds the meaningful constraint of 'up to 25' and clarifies that the strings are Polymarket token IDs, providing context beyond the raw schema.

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 states a specific verb and resource ('Get Polymarket token midpoints') and clarifies scope (up to 25 token ids). It clearly differentiates from the singular sibling 'polymarket_token_midpoint' by the plural and the batch limit. The mention of 'public CLOB' further distinguishes it from other market data tools.

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 context that this is for multiple token ids (up to 25) and explicitly notes it requires no authentication, which helps an agent decide when to use it. It does not explicitly name alternatives, but the plural and limit imply it's the batch version of a single-token tool.

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