Skip to main content
Glama

mailroom_send

Send a new email from a connected mailbox, with plain-text or HTML bodies and optional CC/BCC recipients.

Instructions

Send a new email from a connected mailbox. Plain text by default; HTML when the body contains tags or html=true.

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>",
      "body": "<body>"
    },
    "name": "mailroom_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCc addresses, comma-separated.
toYesRecipient address, or several separated by commas.
bccNoBcc addresses, comma-separated.
bodyYesEmail body.
htmlNoTreat the body as HTML (default: detected from the body).
accountNoWhich connected mailbox to use (its label from mailroom_accounts). Optional when only one is connected or a default is saved in memory.
subjectYesEmail subject.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, and it only discloses the text/HTML body handling — which the schema's html parameter already documents. It says nothing about the fact that sending is irreversible, what permissions or connected-account state are required, failure behavior for invalid recipients, or whether the message is stored in the sent folder.

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?

Two short sentences with the action and the default content-type rule front-loaded. Nothing redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a 7-parameter mutation tool whose schema is fully described, but thin for a send action: no account-selection guidance, no indication of irreversibility, and no distinction from forwarding or from the many sibling send tools. An agent could invoke it, but without knowing the consequences of doing so.

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 every parameter is already documented, and the one piece of description content (text default, HTML when tags present or html=true) restates the html parameter. Baseline 3 applies; no additional semantics beyond the schema are introduced.

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 ('Send a new email') plus the source ('from a connected mailbox'), which separates it from mailroom_read, mailroom_search and mailroom_forward in the same family. The word 'new' implies it is not a reply/forward, but that contrast is left implicit rather than naming mailroom_forward.

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

Usage Guidelines2/5

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

No statement of when to use this versus mailroom_forward, the many other send tools (resend_send_email, gmail_send, sendgrid_send_email), or prerequisites such as a connected mailbox. The only routing hint — the account label from mailroom_accounts — lives in the schema, not the description.

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

Deploy Server

Other Tools