Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket US events

polymarket_us_events_list
Read-onlyIdempotent

List events and their markets from the Polymarket US exchange, filtered by open or closed status. Paginate results with a cursor to browse every event.

Instructions

List events on the separate Polymarket US exchange with their markets. Optional inputs: status, limit and cursor. Returns a list (use cursor when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_us_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEvents per page, 1–100. Default: 20. Each event carries all its markets; pages shift as events open or close, so de-duplicate by `id`.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
statusNoWhich events to list: `open` (default) or `closed`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that events come with their markets embedded and that cursors are used when paginated, which is modest but useful context; it does not discuss ordering or data freshness beyond the schema's note.

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?

Two compact sentences, front-loaded with the resource and scope. The trailing parenthetical about cursors is mildly redundant with the schema's cursor description, but overall the text is tight and well-ordered.

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?

The rich schema and annotation set carry most of the load, and no output schema exists, so the description needn't explain return shape. However, for a paginated open-world listing tool it offers little on pagination semantics or result ordering beyond a passing mention, leaving the description slightly thinner than ideal.

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%, so status, limit, cursor and the context/llm_model fields are all fully documented in the schema itself, including pagination stability and de-duplication by id. The description merely restates the optional input names, adding no meaning beyond the schema.

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 and resource ('List events') and scopes it to 'the separate Polymarket US exchange with their markets', which distinguishes it from the generic polymarket_events_list sibling. It stops short of naming that sibling explicitly, so differentiation requires the agent to infer it from the 'US exchange' qualifier.

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?

The phrase 'separate Polymarket US exchange' implies this tool is for the US venue rather than the global market tools, but there is no explicit when-to-use/when-not-to-use statement or named alternative. The agent must infer the boundary conditions.

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

Deploy Server

Other Tools