Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_token_midpoint

Fetch the current midpoint price for a Polymarket outcome token by token_id. Returns a read-only snapshot with midpoint and fetched_at.

Instructions

Get Polymarket token midpoint. Returns the current midpoint price for one Polymarket outcome token, identified by the required token_id, as a single midpoint number such as 0.285. It is a read-only snapshot, returned with a fetched_at time and the token_id, and is not investment advice.

Input Schema

NameRequiredDescriptionDefault
token_idYesPolymarket CLOB token id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.5/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 load and does reasonably well: it declares the operation read-only ('a read-only snapshot'), specifies the return shape (a single midpoint number plus fetched_at and token_id), and notes snapshot semantics. It stops short of disclosing auth needs, rate limits, or error behavior for an undocumented-annotation tool.

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 sentences, front-loaded with the purpose and return value; nothing is buried. The trailing 'not investment advice' is boilerplate but earns some place on a prediction-market pricing tool.

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 single-parameter read tool with no output schema, the description supplies the missing return-value information (midpoint, fetched_at, token_id) and the read-only nature. It is complete enough to call correctly, though routing against the many Polymarket siblings remains unaddressed.

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 description coverage is 100%, so the schema already documents token_id as 'Polymarket CLOB token id'. The description only restates that it is required and identifies the token, adding no format or sourcing detail beyond the schema, which matches the baseline 3.

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 token midpoint') and clarifies it operates on exactly one token via the required token_id, which implicitly contrasts with the plural polymarket_tokens_midpoints sibling. However, it never names that batch sibling or polymarket_token_price, so the agent must infer the distinction rather than being told.

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 offers no when-to-use or when-not-to-use guidance and names no alternative. With siblings such as polymarket_token_price, polymarket_tokens_midpoints, and polymarket_token_spread sharing the same domain, an agent gets no routing help at all.

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