Skip to main content
Glama

Fetches details for a single Polymarket event by slug

pm_event
Read-only

Fetches details for a single Polymarket event by slug or numeric ID, including all associated markets, outcome tokens, implied probability prices, volume, liquidity, resolution source, rules, and start/end dates. Information only, not financial advice. Related tools on this server, for a different need: pm_history when you need to fetch historical price points for a Polymarket outcome; pm_leaderboard when you need to fetch top-ranked traders on Polymarket ranked by overall. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "pm_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoEvent numeric or unique ID
slugYesEvent slug identifier on Polymarket

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
slugNo
titleNo
activeNo
closedNo
sourceNo
volumeNo
endDateNo
marketsNo
checkedAtNo
liquidityNo
startDateNo
disclaimerNo
descriptionNo
marketsCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds behavior they do not cover: a per-call price of $0.003, the x402/USDC payment requirement across multiple chains, and the fact that failed calls are not charged. That is genuine pre-invocation cost/auth disclosure. It does not discuss rate limits or error behavior, so it stops short of full transparency.

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?

Front-loaded with the substantive sentence about what is fetched, then caveat, alternatives, and pricing in descending priority. 'Information only, not financial advice' is borderline boilerplate but defensible for a prediction-market tool; otherwise there is little waste.

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?

An output schema exists, so the detailed return-value inventory in the description is somewhat redundant but not harmful, and safety metadata is covered by annotations. Payment mechanics, cost, and alternative routing round it out; only edge-case behavior (invalid slug, rate limits) is absent.

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 both parameters carry descriptions, so the baseline is 3. The description's phrase 'by slug or numeric ID' loosely echoes the schema's id/slug split but does not explain that slug is required while id is optional, adding little meaning beyond the 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?

States a specific verb and resource ('Fetches details for a single Polymarket event') and enumerates what the payload contains (markets, outcome tokens, prices, volume, liquidity, rules, dates). It is clearly distinguishable from the named siblings pm_history and pm_leaderboard, so an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent away from this tool for two divergent needs ('pm_history when you need historical price points', 'pm_leaderboard when you need top-ranked traders'), which is real when-to-use-else guidance. It stops short of covering the closest look-alikes such as pm_search or markets, so the routing is helpful but incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources