Skip to main content
Glama

MCPFax Macro & Market Intelligence

by com.mcpscores
OverviewDiscussionsAdmin

Polymarket events

polymarket_events
Read-onlyIdempotent

List Polymarket events — the grouped questions such as an election or a rate decision — ordered by volume, each with title, slug, end date, volume, 24h volume, liquidity, open interest, its full market count and the priced member markets themselves. Use it when a question has many candidate outcomes and you want them together rather than one at a time. Costs $0.005 USDC per call via x402 on Base; an unpaid call returns the payment challenge instead of data, and a call that returns no data is never settled so it costs nothing. Equivalent HTTP route: GET /polymarket/events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many events, 1-25 (default 5) Example: '5'.
closedNoReturn closed events instead of open ones Example: 'false'.
ascendingNoSort ascending instead of descending Example: 'false'.
markets_per_eventNoMember markets per event, 1-25 (default 5) Example: '5'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / ascending / examples
      Added value: +[
+  false
+]
    • addedInput schema / properties / closed / examples
      Added value: +[
+  false
+]
    • addedInput schema / properties / limit / examples
      Added value: +[
+  5
+]
    • addedInput schema / properties / markets_per_event / examples
      Added value: +[
+  5
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds valuable cost and payment behavior: $0.005 USDC via x402 on Base, unpaid calls returning a payment challenge, and no-cost for no-data calls. It also mentions the HTTP route. This goes beyond the annotations and clarifies failure modes.

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 the main action and then usage and cost. No filler; every sentence adds value. The structure is logical: what it does, when to use, cost/payment, and HTTP route.

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?

Complete for a list tool: parameters are fully documented in the schema, annotations cover safety, and the description covers cost, usage, and return fields. No output schema exists, but the description lists the fields returned, which is sufficient for an agent to interpret the response.

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% with each parameter documented including examples and defaults. The description does not add additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate. It does not discuss parameter interactions or edge cases.

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?

Clearly states the tool lists Polymarket events, defines what events are (grouped questions such as elections), and lists the fields returned (title, slug, end date, volume, etc.). This distinguishes it from siblings like polymarket_market or polymarket_markets by focusing on grouped questions rather than individual markets.

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?

Explicitly states when to use: 'Use it when a question has many candidate outcomes and you want them together rather than one at a time.' This implies alternatives like polymarket_market for single outcomes and provides clear guidance without needing to inspect sibling tools.

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

All MCPFax Macro & Market Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources