Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

get_market_by_slug

Fetch a specific Polymarket market by its slug identifier to retrieve market details for a known market reference.

Instructions

Fetch a specific Polymarket market by its slug identifier

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_market_by_slug"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesMarket slug identifier (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Fetch' implies a read-only lookup, but nothing is said about what happens when a slug does not exist (error vs empty), whether the response includes nested event/tag data, or any rate/permission constraints.

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?

A single front-loaded sentence with zero filler; the resource and the lookup key both appear immediately. Nothing needs trimming.

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

Completeness3/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 and no annotations, the description is minimally sufficient to call it correctly. It is thin on failure behavior and return shape, which an agent would need when the slug may be stale or invalid.

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 sole parameter is fully documented in the schema, so the baseline is 3. The description's 'slug identifier' phrasing restates the schema without adding format, case-sensitivity, or sourcing guidance (e.g., where a slug comes from).

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?

States a specific verb ('Fetch') and a specific resource ('a specific Polymarket market') and names the lookup key ('slug identifier'). The singular-resource framing implicitly distinguishes it from list_markets/search_polymarket, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'by its slug identifier' – an agent can infer it should be used when a slug is already known and a bulk/list tool is not appropriate. There is no explicit when-to-use/when-not guidance or named alternative such as get_event_by_slug or list_markets.

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