AIsa Finance

List events

get_polymarket_events

Read-onlyIdempotent

List events with offset based pagination and filter parameters.

Published reference price: $0.00044 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description
`id`	No
`cyom`	No
`slug`	No
`limit`	No
`order`	No	Comma-separated list of fields to order by
`active`	No
`closed`	No
`offset`	No
`tag_id`	No
`archived`	No
`featured`	No
`tag_slug`	No
`ascending`	No
`recurrence`	No
`volume_max`	No
`volume_min`	No
`end_date_max`	No
`end_date_min`	No
`include_chat`	No
`related_tags`	No
`liquidity_max`	No
`liquidity_min`	No
`exclude_tag_id`	No
`start_date_max`	No
`start_date_min`	No
`include_template`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / closed / oneOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "enum": [
+      "any"
+    ],
+    "type": "string"
+  }
+]

removedInput schema / properties / closed / type
```
Removed value: -"boolean"
```

Changed31 schema fields changedOct 15, 2026
- removedInput schema / properties / active / description
```
Removed value: -"Filter by active events."
```
- removedInput schema / properties / archived / description
```
Removed value: -"Filter by archived events."
```
- removedInput schema / properties / ascending / description
```
Removed value: -"Sort ascending when true."
```
- removedInput schema / properties / ascending / example
```
Removed value: -false
```
- removedInput schema / properties / closed / description
```
Removed value: -"Filter by whether the event is closed."
```
- addedInput schema / properties / cyom
```
Added value: +{
+  "type": "boolean"
+}
```
- removedInput schema / properties / end_date_max / description
```
Removed value: -"Filter events ending before this ISO timestamp."
```
- removedInput schema / properties / end_date_min / description
```
Removed value: -"Filter events ending after this ISO timestamp."
```
- addedInput schema / properties / exclude_tag_id
```
Added value: +{
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}
```
- removedInput schema / properties / featured / description
```
Removed value: -"Filter by featured events."
```
- removedInput schema / properties / id / description
```
Removed value: -"Filter by one or more event IDs."
```
- addedInput schema / properties / include_chat
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / include_template
```
Added value: +{
+  "type": "boolean"
+}
```
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum number of events to return."
```
- removedInput schema / properties / limit / example
```
Removed value: -20
```
- removedInput schema / properties / liquidity_max / description
```
Removed value: -"Maximum liquidity."
```
- removedInput schema / properties / liquidity_min / description
```
Removed value: -"Minimum liquidity."
```
- removedInput schema / properties / offset / description
```
Removed value: -"Number of events to skip for offset-based pagination."
```
- removedInput schema / properties / offset / example
```
Removed value: -0
```
- changedInput schema / properties / order / description
```
Previous value: -"Comma-separated list of fields to order by."New value: +"Comma-separated list of fields to order by"
```
- removedInput schema / properties / order / example
```
Removed value: -"volume"
```
- addedInput schema / properties / recurrence
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / related_tags
```
Added value: +{
+  "type": "boolean"
+}
```
- removedInput schema / properties / slug / description
```
Removed value: -"Filter by one or more event slugs."
```
- removedInput schema / properties / start_date_max / description
```
Removed value: -"Filter events starting before this ISO timestamp."
```
- removedInput schema / properties / start_date_min / description
```
Removed value: -"Filter events starting after this ISO timestamp."
```
- removedInput schema / properties / tag_id / description
```
Removed value: -"Filter by tag ID."
```
- removedInput schema / properties / tag_slug / description
```
Removed value: -"Filter by tag slug."
```
- removedInput schema / properties / tag_slug / example
```
Removed value: -"sports"
```
- removedInput schema / properties / volume_max / description
```
Removed value: -"Maximum volume."
```
- removedInput schema / properties / volume_min / description
```
Removed value: -"Minimum volume."
```
First observedSep 15, 2026

TDQS

C2.4/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description does add one behavioral fact beyond the annotations, that pagination is offset-based, which matters for how the agent pages through results, but it says nothing about result volume, defaults, or how the many filters combine.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one functional sentence is front-loaded and waste-free, but it is drastically under-sized for a 26-parameter listing tool, so brevity here is under-specification rather than conciseness. The injected pricing block is boilerplate that contributes nothing to tool selection or invocation.

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 presence of an output schema means return values need not be described, which removes one expected burden. Even so, a 26-parameter, zero-required filtering tool with no sibling differentiation and no parameter or pagination-detail guidance is not complete enough for confident selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 26 parameters with only 4% description coverage, so the description carries nearly the full burden of explaining them. Instead it offers only the generic phrase 'filter parameters' and names none of them; the agent gets no meaning for id, slug, cyom, recurrence, related_tags, the volume/liquidity/date bounds, or the closed:'any' union type.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource ('List events') and adds the pagination style ('offset based') and that filters exist. However, it does nothing to separate this tool from the sibling get_polymarket_markets or get_polymarket_activity, so an agent must guess whether 'events' vs 'markets' is the right resource.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of prerequisites, and no naming of alternatives among the eleven siblings. The mention of 'filter parameters' implies the tool supports narrowing, but nothing tells the agent when this tool is preferred over get_polymarket_markets.

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

All AIsa Finance tools Inspect

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

Need Help?