Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_token_spread

Fetch the current bid-ask spread for a Polymarket outcome token by token ID, returning a read-only spread number and timestamp for quick market analysis.

Instructions

Get Polymarket token spread. Returns the current bid-ask spread for one Polymarket outcome token, identified by the required token_id, as a single spread number. It is a read-only snapshot with a fetched_at time 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?

No annotations are provided, so the description must carry behavioral context. It usefully discloses that this is a read-only snapshot, includes a `fetched_at` time, returns a single `spread` number, and is not investment advice; it does not mention authentication, rate limits, or error behavior, but covers the core traits for a simple market-data read.

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?

The description is three compact sentences and front-loads the purpose before the return details and disclaimer. The 'not investment advice' sentence is boilerplate but short, and the overall definition has little waste.

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-parameter read tool with no output schema, the description is largely complete: it explains the returned value (`spread`), includes freshness metadata (`fetched_at`), and states the read-only nature. It could be stronger by naming when to prefer sibling spread or price tools, but the essential context is present.

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%, and the schema already documents `token_id` as a 'Polymarket CLOB token id'. The description adds that the identifier is required and refers to one outcome token, but it does not add format examples or selection guidance beyond the schema.

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?

The description states a specific verb and resource: retrieving the current bid-ask spread for one Polymarket outcome token. It also says the result is a single `spread` number, which implicitly separates it from batched siblings like `polymarket_tokens_spreads`, but it does not explicitly name or contrast any sibling tool.

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 explains that a `token_id` is required and that the tool returns the spread for one token, but it gives no explicit guidance on when to use this tool versus alternatives such as `polymarket_token_midpoint`, `polymarket_token_orderbook`, or `polymarket_tokens_spreads`. It states what the tool does, not when an agent should choose it.

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