list_recent_eventsAuthenticated tool for inspecting recent received events, duplicates, and signature status.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| limit | No | ||
| sourceId | No | ||
| signatureStatus | No | ||
| failedDeliveryOnly | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds minimal behavioral context beyond 'Authenticated'. The description hints at filtering by signature status and duplicates but doesn't elaborate on pagination or scope of 'recent'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, very concise. However, it may be too brief given the tool's complexity, sacrificing necessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, no description of return values, and parameter semantics are missing. The description only covers the tool's purpose superficially, leaving significant gaps for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage and 5 parameters, the description provides no explanation for any parameter (q, limit, sourceId, signatureStatus, failedDeliveryOnly), leaving the agent to guess their purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool inspects recent received events, including duplicates and signature status, aligning with the name 'list_recent_events' and distinguishing it from sibling tools like get_event_detail (single event) or list_messages.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as get_event_detail or list_messages, nor are there any prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is some overlap between `list_messages`, `list_recent_events`, and `list_message_attempts`, and between `replay_event` and `replay_events`. However, the descriptions generally clarify differences.
The naming mostly follows a verb_noun pattern (create_, list_, get_, update_, delete_), with consistent snake_case. A few tools like `rotate_endpoint_secret` and `upsert_event_type` deviate but still use verb_noun structure.
With 52 tools, the set is extremely large and may overwhelm agents. While the domain is complex, this many tools reduce coherence and make selection more difficult.
The tool surface is very comprehensive, covering CRUD for most resources, replay, retries, anomaly management, and webhook setup. Minor gaps exist (no delete for destinations, no update for sources), but core workflows are well-supported.