Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

get_event_by_slug

Fetch a specific Polymarket event by its slug identifier to retrieve event details for market research or event tracking.

Instructions

Fetch a specific Polymarket event 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_event_by_slug"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesEvent 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, yet it only restates the fetch action. It says nothing about what happens with an unknown or stale slug, whether the lookup is cached, whether any auth or rate limit applies, or what the payload contains.

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?

One sentence, front-loaded with the action and resource, with zero filler. Appropriately sized for a single-parameter lookup tool.

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 simple read-by-key tool with a fully documented single parameter this is close to sufficient, but with no output schema the description offers no hint of what an event record contains or how failures surface. Those gaps are minor but real for an agent deciding whether the call will answer its question.

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 coverage is 100% and the single parameter is fully described as "Event slug identifier (required)", so the schema already does the work. The description adds no format, casing, or example guidance beyond that baseline.

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?

"Fetch a specific Polymarket event by its slug identifier" states a concrete verb (fetch) and a concrete resource (event), and the "by its slug" qualifier separates it from the list_events / search_polymarket style tools. It stops short of explicitly contrasting with get_market_by_slug, so an agent must infer the event-vs-market distinction from the resource word alone.

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: the agent must already hold a slug to call this, which implicitly means it comes after a listing/search call. There is no explicit when-to-use, when-not-to-use, or named alternative for retrieving an event by other means.

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