Skip to main content
Glama

List recent events

list_events
Read-onlyIdempotent

Returns the member's event feed for the last 7 days, newest first (limit 1 to 200): post.published, post.failed, reply.sent, patrol.reply, patrol.pending, token.expiring, usage.threshold, approval.decided. since (ISO 8601) returns only newer events; types filters by name. Each call counts against the daily quota even when nothing is new, so poll sparingly (every 30 minutes on the free plan). Applies when the user asks what happened recently or whether a post went out.

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
limitNo1-200
sinceNoISO 8601
typesNoComma-separated event names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the traits they can't: every call consumes daily quota even when empty, recommended polling cadence, newest-first ordering, and a fixed 7-day window. That is exactly the beyond-annotation context an agent needs before polling in a loop.

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?

Dense and front-loaded: purpose, window, ordering, event types, then params, then quota, then usage trigger. Nearly every clause earns its place, though the middle param sentence is somewhat telegraphic and the whole thing reads as a single long run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description still specifies what comes back (feed of named event types, newest first, capped at 200) and how to page through time via since. Combined with the quota warning, an agent has everything needed to call this correctly and responsibly.

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 coverage is 100% and the schema entries are terse ('1-200', 'ISO 8601', 'Comma-separated event names'), so the baseline is 3. The description adds real semantics: since returns only newer events (incremental fetch), types filters by event name, and limit caps the feed at 1–200.

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?

States a specific verb+resource ('Returns the member's event feed'), the window (last 7 days), the ordering (newest first), and enumerates the exact event types returned. An agent can tell this apart from siblings like list_pending_replies or get_my_usage without opening any schema.

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

Usage Guidelines4/5

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

Explicitly says when to use it: 'Applies when the user asks what happened recently or whether a post went out,' and warns to poll sparingly (every 30 minutes on the free plan). It does not name alternative tools or when-not-to-use conditions, which keeps it from a 5.

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.