Skip to main content
Glama
Birantx

polymarket-mcp-server

by Birantx

Get Polymarket market detail

get_market

Retrieve complete details and live CLOB midpoint and spread for a single prediction market using its numeric ID or slug.

Instructions

Fetch full detail for a single market by numeric ID or slug, enriched with a live CLOB midpoint and spread for each outcome token. Use after search_markets when you need depth on one specific market.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMarket numeric ID (e.g. '703258') or slug (e.g. 'will-jesus-christ-return-before-2027')
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that response includes live CLOB midpoint and spread. No annotations provided, so description carries full burden; could mention auth or side effects but is sufficient for a read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: first states action and enrichment, second gives usage context. No wasted words.

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

Completeness5/5

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

Complete for a single-parameter tool; covers input format, output enrichment, and usage sequence relative to siblings. No output schema needed as description explains response key features.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds value to the schema by explaining the parameter can be either numeric ID or slug, beyond the schema's generic description. Schema coverage is 100%, so this is extra context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool fetches full detail for a single market by ID or slug, enriched with CLOB midpoint and spread. Distinguishes from siblings like search_markets which returns multiple markets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises to use after search_markets when needing depth on one specific market, providing clear when-to-use context and excluding use for multiple markets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Birantx/polymarket-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server