Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_market_liquidity

Retrieve a Polymarket market's public liquidity snapshot by market ID, combining market details and CLOB data when token IDs exist; no trading or auth required.

Instructions

Get Polymarket market liquidity. Returns a public market liquidity snapshot that joins market detail with public CLOB market data when token ids are available. This endpoint is not a trading endpoint and does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.

Input Schema

NameRequiredDescriptionDefault
idYesPolymarket market id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

B3.2/5.0
Behavior3/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 disclose a genuinely useful trait: this is a public, non-trading read that requires no user token, signature, cookies, or account auth. However it says nothing about return shape, pagination, rate limits, or what happens when token ids are unavailable.

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?

Purpose is front-loaded in the first sentence and the description stays short. The auth enumeration (token, signature, cookies, account) is slightly repetitive but serves to preempt auth questions, so it largely earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-param, no-annotation tool, the description establishes that it is a safe public read, which is the main ambiguity. It is missing any indication of the returned liquidity snapshot's contents, though with no output schema an agent could reasonably want that.

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% and the single `id` parameter is documented as the market id, so the schema does the work. The description's mention of 'token ids available' hints at a linkage but adds no real meaning beyond the schema; baseline 3 applies.

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 and resource (get Polymarket market liquidity) and adds that it joins market detail with public CLOB data. It does not explicitly distinguish itself from tightly-related siblings like polymarket_market_detail or polymarket_clob_market, so an agent still has to infer which to pick.

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?

There is no when-to-use guidance or named alternative among the many polymarket_* siblings. The 'when token ids are available' clause describes internal behavior, not when an agent should choose this tool over others.

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