Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_token_price

Get current Polymarket outcome token price using token_id and optional buy/sell side, returning a snapshot price and fetched_at timestamp.

Instructions

Get Polymarket token price. Returns the current price for one Polymarket outcome token, identified by the required token_id. side is buy or sell and defaults to buy. The response gives the price as a number, the side used and a fetched_at time. It is a snapshot, not trading advice.

Input Schema

NameRequiredDescriptionDefault
sideNoOrder side used for the CLOB price
token_idYesPolymarket CLOB token id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / side / enum
      Added value: +[
+  "buy",
+  "sell"
+]
  2. Addedv1.1.0

TDQS

B3.4/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, but it does disclose useful traits: this is a read snapshot (not history or streaming), returns a point-in-time value, and is 'not trading advice.' It omits auth requirements, rate limits, and freshness guarantees, so it is only partially complete for a data tool with zero annotation coverage.

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?

It is front-loaded with the purpose, then parameters, then return shape, then a caveat, with no wasted sentences. Slightly more verbose than strictly necessary but each sentence contributes.

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?

With no output schema, the description appropriately documents the return (price as number, side, fetched_at). For a simple two-parameter read tool with no annotations this is nearly complete, lacking only operational details like permissions or freshness.

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%, so baseline is 3, but the description adds value beyond the schema by stating that `token_id` is required and that `side` defaults to `buy` (a default the schema itself does not declare). It restates the buy/sell enum without adding further meaning.

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 gives a specific verb+resource ('Get Polymarket token price... current price for one Polymarket outcome token'), which is clear on its own. However, it never distinguishes this from close siblings like polymarket_token_midpoint, polymarket_token_spread, or polymarket_token_price_history, so an agent can't tell from the text why to pick this over those.

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 or when-not-to-use guidance and no alternatives named. It states the required parameter but offers no context about which price/midpoint/spread tool to select for a given need, leaving selection entirely to inference.

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