Skip to main content
Glama

Hail Communication for AI

Send an email

send_email

Send an email from a verified workspace sender.

    Plain-text emails still have sending, delivery and bounce events.

    Without ``from_``, one verified custom domain takes priority over the Hail mail address.
    Several verified custom domains require an explicit ``from_`` address.
    A custom domain blocked from sending (``sends_enabled`` false, PATCH ``/v1/email-domains/{id}``) is skipped for picks and refuses an explicit ``from_``.
    When configured, a workspace without a sender receives a Hail mail address automatically.

    Hail does not verify consent.

    Returns the email ID, status, sender, recipients and ``idempotency_key``, or an error.
    

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>",
      "recipient_consent": "<recipient_consent>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoEmail addresses to copy; every recipient sees them.
toYesEmail addresses of the people the message is for.
bccNoEmail addresses to copy in secret: they get the message, and no other recipient sees their addresses.
from_NoSender address. It must match a verified identity from ``list_email_domains``; on a custom domain any local part works. Omitted: the workspace default sender.
subjectYesSubject line the recipients see in their inbox.
metadataNoFree-form JSON object stored on the email record.
reply_toNoAddress that receives replies instead of the sender. Omitted: replies go to the sender.
body_htmlNoThe message as HTML. Open and click tracking works only with an HTML body. Give this, ``body_text``, or both.
body_textNoThe message as plain text, shown by mail apps that cannot display HTML. Give this, ``body_html``, or both.
from_nameNoDisplay name for the From header, such as ``Acme Billing``. Control characters are rejected.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
message_typeNo``informational`` for transactional or service messages, or ``marketing``.informational
attachment_idsNoAttachment IDs: the ``id`` from ``upload_email_attachment``, or from ``create_file_upload`` with purpose ``email_attachment``.
consent_sourceNoWhere or how consent was obtained, such as ``signup form``. Required when ``message_type`` is ``marketing``.
idempotency_keyNoRetry key. The ``idempotency_key`` from an earlier response refers to that original request instead of starting a new one. Omitted: a new key is generated and returned.
recipient_consentYesAttestation that the recipient lawfully agreed to be contacted, as the user confirmed it. Hail does not check it; only ``true`` is accepted.
consent_obtained_atNoWhen consent was obtained, as an ISO 8601 timestamp, if known.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / from_name / description
      Previous value: -"Display name for the From header, such as ``Acme Billing``."New value: +"Display name for the From header, such as ``Acme Billing``. Control characters are rejected."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed12 schema fields changed
    • changedInput schema / properties / bcc / description
      Previous value: -"Bcc email addresses."New value: +"Email addresses to copy in secret: they get the message, and no other recipient sees their addresses."
    • changedInput schema / properties / body_html / description
      Previous value: -"HTML body. Open and click tracking requires it."New value: +"The message as HTML. Open and click tracking works only with an HTML body. Give this, ``body_text``, or both."
    • changedInput schema / properties / body_text / description
      Previous value: -"Plain-text body."New value: +"The message as plain text, shown by mail apps that cannot display HTML. Give this, ``body_html``, or both."
    • changedInput schema / properties / cc / description
      Previous value: -"Cc email addresses."New value: +"Email addresses to copy; every recipient sees them."
    • changedInput schema / properties / from_name / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 256,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / recipient_consent / description
      Previous value: -"Attestation that the recipient lawfully consented to this contact. Only ``true`` is accepted."New value: +"Attestation that the recipient lawfully agreed to be contacted, as the user confirmed it. Hail does not check it; only ``true`` is accepted."
    • changedInput schema / properties / reply_to / description
      Previous value: -"Reply-To email address. Omitted: no Reply-To header."New value: +"Address that receives replies instead of the sender. Omitted: replies go to the sender."
    • changedInput schema / properties / subject / description
      Previous value: -"Subject line."New value: +"Subject line the recipients see in their inbox."
    • addedInput schema / properties / subject / maxLength
      Added value: +998
    • addedInput schema / properties / subject / minLength
      Added value: +1
    • changedInput schema / properties / to / description
      Previous value: -"Recipient email addresses; at least one."New value: +"Email addresses of the people the message is for."
    • addedInput schema / properties / to / minItems
      Added value: +1
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag openWorldHint=true and non-read-only, so the description focuses on what those annotations cannot convey: plain-text messages still generate delivery and bounce events, sender-resolution precedence, blocked-domain behavior, that consent is unverified, and the shape of the success response (id, status, sender, recipients, idempotency_key). Mentioning idempotency_key alongside idempotentHint=false is consistent, since retry-safety is opt-in via the key rather than default behavior.

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?

The send action and sender rules are front-loaded, and each paragraph carries a distinct concern (sending events, sender resolution, consent, return value). It is dense but not padded; the plain-text-bounce sentence is the weakest, adding operational context rather than a decision-relevant fact.

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 17-parameter mutation tool, the description covers the three things an agent most needs and the schema cannot supply: which sender will be used, what compliance posture is assumed, and what comes back. Attachment IDs and marketing consent fields are documented in the schema, and an output schema exists, so nothing critical is left to inference.

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; the description earns above that by explaining the fallback logic for 'from_' (priority among custom domains, hard requirement when several exist, refusal on blocked domains) and by framing recipient_consent as an attestation the caller must truthfully supply. It adds real meaning beyond the per-field schema text, though it does not touch most of the other 17 parameters.

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 first sentence states a specific verb and resource ('Send an email') plus a scope qualifier ('from a verified workspace sender'), which immediately distinguishes it from the read-side siblings (get_email, list_emails) and from send_sms. An agent can identify the operation without opening the 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?

It gives concrete selection rules for the sender: omitted 'from_' falls back to a workspace default with custom-domain priority, multiple verified domains force an explicit 'from_', and blocked domains are skipped or refused. It also warns that Hail does not verify consent, implying the caller must. It stops short of naming alternatives or stating when not to send (e.g., prefer SMS), so it is clear context rather than full routing 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