Skip to main content
Glama

Send transactional email

email_send
Destructive

Sends ONE transactional email (a receipt, a reply, a booking confirmation) to one address right away. Not reversible, and it uses one email of quota. Never use it for marketing or to mail a list: campaigns are for that. Show the person the recipient, subject and body and get a yes before calling, then pass confirm: true. idempotency_key is required: reuse the same key if you retry so the email is not sent twice. Pass html, text, or both. Requires API key scope: send.

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": {
      "to": "<to>",
      "subject": "<subject>",
      "idempotency_key": "<idempotency_key>",
      "confirm": "<confirm>"
    },
    "name": "email_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address.
htmlNoHTML body (at most 200,000 characters). Hollerpost adds the brand header.
textNoPlain text body (at most 50,000 characters).
confirmYesMust be true, and only after the person explicitly approved this exact recipient, subject and body. Never set it on a guess.
subjectYesSubject line.
reply_toNoReply-to address, if different from the workspace default.
idempotency_keyYesA unique key for this email, for example "receipt-1042". Reusing it returns the first result instead of sending again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the supplied annotations by disclosing consequences (not reversible), cost (consumes one email of quota), auth requirement (API key scope: send), and a retry contract tied to idempotency_key. There is a mild tension with idempotentHint=false, but the annotation describes default behavior while the description describes client-supplied-key idempotency, so it is not a contradiction.

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?

Five short sentences, front-loaded with identity and irreversibility, then exclusions, then the confirmation protocol, then the idempotency rule. Every sentence carries a distinct, actionable constraint and none are redundant with each other.

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?

For a destructive, open-world, quota-consuming action with no output schema, the description covers the safety, cost, auth and retry concerns an agent needs before calling. The one gap is what a successful send returns (an id or status), which an agent would otherwise have to infer since no output schema exists.

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%, so the baseline is 3, but the description adds real meaning the schema lacks: 'Pass html, text, or both' clarifies the body-parameter relationship (neither is marked required and no oneOf exists), and it re-emphasizes reuse-the-same-key retry semantics. It doesn't add anything about reply_to, which is left entirely to the schema.

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 and resource plus hard scope: 'Sends ONE transactional email ... to one address right away', with concrete examples (receipt, reply, booking confirmation). It also explicitly separates itself from the bulk/marketing path ('campaigns are for that'), so an agent can choose between it and the campaign siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives both sides of the routing decision: use for one-off transactional mail, never for marketing or list mail, and a named alternative category for that case. It also adds a procedural precondition ('Show the person the recipient, subject and body and get a yes before calling') that tells the agent exactly when it is allowed to invoke.

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