Fetch normalized details for a Polymarket event by slug using public Gamma JSON, no token, wallet, or authentication required.
Get Polymarket event detail. Returns one normalized Polymarket event from credential-free public Gamma event JSON. This endpoint does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Polymarket event slug |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description bears full responsibility. It states the endpoint requires no user token or auth, which is helpful, but does not disclose rate limits, error handling, or what 'normalized' means. Adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two sentences that immediately convey the core function and key attributes. No redundant information; front-loaded with the verb and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one parameter and no output schema, the description adequately explains the input and basic behavior. It lacks details about the return structure but is sufficient for a simple retrieval tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%—the single parameter 'slug' is described as 'Polymarket event slug' in the schema. The description adds context about the data source but does not provide additional semantics beyond the schema definition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get Polymarket event detail.' It specifies the data source (public Gamma event JSON) and that it returns one normalized event, distinguishing it from list tools like polymarket_events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description notes no authentication is required, implying public access, but fails to provide guidance on when to use this tool versus siblings like polymarket_market_detail or polymarket_events. No explicit when-to-use or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.