Skip to main content
Glama

Recent delivery events

events_recent
Read-onlyIdempotent

Lists recent delivery events of one type across campaigns and transactional mail: email.bounced (default), email.complained or email.delivered. Free and read only. Useful for list hygiene and deliverability questions. Requires API key scope: read.

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": "events_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoEvent type (default email.bounced).
limitNoHow many events (1 to 100, default 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so 'Free and read only' is largely redundant. The one genuinely additive fact is the required API key scope of 'read'; nothing is said about how far back 'recent' extends, what ordering is returned, or rate/cost behavior beyond 'free'.

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?

Three short sentences, front-loaded with what the tool does and what it accepts, with the auth requirement last. Minor waste exists in repeating the enum values and the read-only/free claim that the annotations already carry.

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?

With only two optional parameters, rich annotations, and no output schema, the definition covers selection and invocation adequately. The remaining gap is that, absent an output schema, an agent gets no hint about what fields an event record contains or how far back the 'recent' window reaches.

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%, with both parameters documented including the enum values and the 1-100 range for limit. The description only restates the default type and implies a single type per call, adding no syntax or semantics beyond the schema; baseline 3 applies.

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 ('Lists recent delivery events') and narrows scope to 'across campaigns and transactional mail', plus enumerates the three allowed event types. It is clear what the tool returns, but it never names the nearby 'event_list' tool to disambiguate delivery events from any other kind of event.

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?

Gives concrete use cases ('list hygiene and deliverability questions') and a precondition ('Requires API key scope: read'), which tells an agent when the tool is appropriate. It stops short of exclusions or naming an alternative for broader event history, so there is no explicit when-not guidance.

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.

Resources