Skip to main content
Glama
Sign In

CoinMarketCal

by com.coinmarketcal
OverviewDiscussionsAdmin

List events

list_events

Returns a paginated list of upcoming and historical events within the date window available to the caller's plan. Default sort is date asc (soonest first). The coins, categories, and date filters compose with AND.

Input Schema

NameRequiredDescriptionDefault
toNoInclusive upper bound on `date`. Default = today + tier upcoming window (e.g. 7 days on Free, 90 days on Standard, full on Pro+).
fromNoInclusive lower bound on `date`. Default = today. Free and Standard clamp past values to today; Pro clamps them to the previous 30 days; Elite and Enterprise can query the complete public catalog history since 2017.
coinsNoComma-separated coin **slugs** (e.g. `bitcoin,ethereum`). Tickers are accepted but **strongly discouraged**; symbols collide across coins (e.g. `UNI` resolves to several different projects). Use `GET /v2/coins` to look up canonical slugs.
limitNoPage size (1–100).
cursorNoOpaque pagination cursor returned in the previous response's `meta.cursor`.
sortByNoSort order. Default `date_asc` (soonest first). `impact_desc` is Elite+ only; lower tiers receive 403. It lists conferences, which have no score, last.
keywordNoFree-text search across event title and description. Case-insensitive substring match.
impactMinNoLower bound on the precise impact score (0.0–10.0). Elite+ only; lower tiers receive 403. Excludes conferences, which have no score.
categoriesNoComma-separated category ids. Case-insensitive. Standard+ only; Free requests using this filter return 403. Use `GET /v2/categories` to look up the canonical id list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / impactMin / description
      Previous value: -"Lower bound on the precise impact score (0.0–10.0). Elite+ only; lower tiers receive 403."New value: +"Lower bound on the precise impact score (0.0–10.0). Elite+ only; lower tiers receive 403. Excludes conferences, which have no score."
    • changedInput schema / properties / sortBy / description
      Previous value: -"Sort order. Default `date_asc` (soonest first). `impact_desc` is Elite+ only; lower tiers receive 403."New value: +"Sort order. Default `date_asc` (soonest first). `impact_desc` is Elite+ only; lower tiers receive 403. It lists conferences, which have no score, last."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully states pagination, plan-dependent date windows, default sorting, and AND composition of filters, but it omits the 403/tier constraints for impactMin, categories, and impact_desc sorting, and does not describe authentication or return shape.

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?

Three sentences, front-loaded with purpose and scope, then default sort and filter composition. Every sentence adds useful information with no visible padding.

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?

For a 9-parameter listing tool with no annotations and no output schema, the description covers purpose, pagination, plan-dependent date scope, default sort, and filter composition. It leaves tier/403 details and return-shape specifics to the schema or inference, which are minor gaps given the rich input schema.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds non-obvious meaning by stating that coins, categories, and date filters compose with AND, and it reinforces the default date_asc sort, which supplements the schema’s parameter-level documentation.

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: returns a paginated list of upcoming and historical events, scoped by the caller's plan date window. It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as get_event or list_event_cancellations.

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 description supplies useful context about plan-based date windows, default sort, and AND-composed filters, implying this is the listing/search tool. However, it does not explicitly say when to use this instead of get_event or list_event_cancellations, nor does it state any when-not conditions.

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

All CoinMarketCal 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