Skip to main content
Glama
Sign In

Nextmail

by sh.nextmail
OverviewDiscussionsAdmin

Send contact event

sendContactEvent
Destructive

Record that something happened to one contact, such as order.placed or trial.started. Every live automation that starts on that event name takes the contact in, so its emails start going to them, and a wait step holding out for the name moves on. The answer says which automations it started. Events are kept for 90 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "email": "<email>"
    },
    "name": "sendContactEvent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWhat happened, such as order.placed: letters, digits, dots, colons, dashes and underscores. Names are matched exactly, case included.
emailYesThe contact the event is about, by email address.
occurredAtNoWhen it happened, as an ISO 8601 instant. Left out, it is now. Not in the future, and at most 90 days ago.
propertiesNoDetails of the event as a JSON object, at most 50 keys and 4 KB. An event trigger can filter on them and steps can use them, except a property named email, which never reaches the steps.
contactNameNoThe name to give a contact that createContact adds.
createContactNotrue adds the address to the contacts when nobody has it yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

It clearly discloses the side effects: live automations starting on the event name enroll the contact, emails begin sending, and wait steps advance. It also states the response identifies which automations started and that events are retained for 90 days, which adds meaningful context beyond the destructive/open-world annotations.

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?

The description is front-loaded with the core action and scope, then explains consequences, response behavior, and retention in compact sentences. Every sentence contributes useful information without repetition.

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?

For a six-parameter tool with a nested properties object, the schema covers parameter details thoroughly and the description covers the important behavioral consequences and response shape. With no output schema, saying that the answer names the started automations is sufficient for correct invocation.

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 six parameters are already well documented. The description adds little parameter-specific meaning beyond noting the 90-day retention, which the occurredAt schema already covers.

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?

The description uses a specific verb-resource pair, 'Record ... something happened to one contact,' and gives concrete event-name examples. The explicit 'one contact' scope also distinguishes it from the plural sibling sendContactEvents without requiring the schema to be opened.

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?

Usage is implied by the fact that the tool records an event and triggers automations waiting on that name. However, the description does not explicitly state when to use this tool versus alternatives such as sendContactEvents, nor does it give exclusions or preconditions.

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

All Nextmail toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources