Skip to main content
Glama

List events

list_events
Read-onlyIdempotent

List recent events (message.sent/delivered/failed/received, number.purchased/released, ...), newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly events of this type, like message.delivered
limitNoMax results (default 25, max 100)
cursorNonext_cursor from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / type / description
      Added value: +"Only events of this type, like message.delivered"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is fully covered structurally. The description adds genuinely new context — 'recent' windowing and newest-first ordering — but says nothing about whether 'recent' is bounded, how far back pagination reaches via cursor, or the shape of an event object.

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?

A single sentence that front-loads the verb and resource, then the ordering guarantee. No filler. Docked one point because the trailing '...' leaves the event-type list open-ended without saying where the full set is defined.

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?

For a simple three-parameter read-only list tool this is nearly sufficient, and no output schema exists to require return-value explanation. Still, it omits what an event record contains and whether the 'recent' window limits pagination depth — details an agent polling for a specific event would need.

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 all three parameters are documented (type, limit with defaults/max, cursor referencing next_cursor). The description's parenthetical enumeration of message.* and number.* event types adds useful vocabulary beyond the schema's single 'message.delivered' example, but it is illustrative and non-exhaustive ('...'), so it cannot be treated as an authoritative enum. Baseline 3 is appropriate.

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 (List) and resource (events) and scopes it to 'recent' with 'newest first' ordering, plus concrete event-type examples. However, it does not distinguish this generic event stream from siblings like list_audit_logs, get_integration_events, or list_webhook_deliveries, so an agent has no basis to choose among them from the description alone.

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?

No when-to-use guidance is given — nothing says when to prefer this over wait_for_events (polling vs waiting), get_integration_events (integration-scoped), or list_audit_logs (admin actions). The only implicit signal is the word 'recent'. The agent must infer the routing decision entirely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.