Retrieve the public CLOB bid-ask spread for a specified Polymarket token ID to compare buy and sell prices and gauge market depth.
Get Polymarket token spread. Returns the public CLOB spread for one Polymarket token id.
| Name | Required | Description | Default |
|---|---|---|---|
| token_id | Yes | Polymarket CLOB token id |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It only states the tool returns the spread, but does not mention rate limits, authentication needs, or any side effects. No behavioral traits beyond basic function are described.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long with no unnecessary information. It is front-loaded with the core purpose and immediately conveys the function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description provides the basic purpose but does not explain what 'spread' represents or the format of the return value. This could leave the agent uncertain about how to interpret the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the parameter 'token_id' already described as 'Polymarket CLOB token id'. The description adds no additional meaning beyond what is in the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool retrieves the public CLOB spread for one Polymarket token id. The verb 'Get' and resource 'Polymarket token spread' are specific and distinguish this from sibling tools like polymarket_token_midpoint or polymarket_token_price.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, conditions, or exclusions, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.