Skip to main content
Glama
pr1m8

polymarket-mcp

by pr1m8

gamma_get_market_by_slug

Retrieve a single market's details using its unique slug. Ideal after identifying the correct market through search, providing precise market data.

Instructions

Fetch one canonical market by its slug.

Use this tool when you already know the exact market slug and want the clearest single-market lookup. This is the preferred tool after a search step has identified the correct market.

Do not use this tool for broad discovery across a topic; use search_public or list_markets first in that case. The slug should be the market slug string from the Polymarket URL path, not the full URL.

This tool is often followed by CLOB book or price lookups if you want live market state, or by event lookup if you want the parent event context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesCanonical market slug from a Polymarket market URL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYesNormalized Polymarket market model. Args: id: Optional upstream market identifier. slug: Canonical market slug from Polymarket URLs. question: Human-readable market question text. active: Whether the market is currently active. closed: Whether the market is closed. liquidity: Reported liquidity value when present. volume: Reported volume value when present. event_slug: Parent event slug when known. clob_token_ids: Associated CLOB token identifiers, if available. Returns: Market: Normalized market model. Raises: ValueError: If validation fails. Examples: >>> market = Market(slug="fed-decision", question="Will the Fed cut?") >>> market.slug 'fed-decision'
Behavior4/5

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

No annotations provided, so description carries full burden. It clarifies the operation is a fetch (read-only), specifies slug format (not full URL), but does not disclose potential errors, rate limits, or auth requirements. However, the output schema exists, reducing need for return format details.

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?

Four sentences, front-loaded with main purpose, then usage guidance, caveat, and follow-up hints. No redundant or irrelevant information.

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?

For a simple lookup tool with one parameter and an output schema, the description covers purpose, usage, parameter meaning, and typical follow-ups. Complete given the context signals.

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?

Schema description coverage is 100%, and description adds value by explaining 'Canonical market slug from a Polymarket market URL' and emphasizing it's the path slug, not full URL. This context goes beyond schema.

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?

Description explicitly states 'Fetch one canonical market by its slug', which is a specific verb+resource. It distinguishes from sibling tools like gamma_search_public and gamma_list_markets by noting it's for exact slug lookup after a search step.

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?

Provides clear when-to-use ('when you already know the exact market slug'), when-not-to-use ('Do not use... for broad discovery'), and alternatives ('use search_public or list_markets first'). Also suggests follow-up tools.

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/pr1m8/polymarket-mcp'

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