Skip to main content
Glama

Send email

send_email

Send one transactional email from a verified domain on the account. Not for bulk or marketing email.

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": {
      "from": "<from>",
      "to": "<to>",
      "subject": "<subject>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
fromYesSender, for example "Shop <noreply@example.com>"
htmlNoHTML body
textNoPlain text body
subjectYes
reply_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them: the sender must be a verified domain on the account. It omits other material behavior such as suppression-list handling, rate limits, and failure modes for an unverified sender.

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, front-loaded with the core action and followed immediately by the exclusion. Every clause carries information; nothing is padded or restated from the title.

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?

Reasonable for a simple send operation, since the verified-domain prerequisite and transactional-only scope are stated. However, with 8 parameters, no output schema, and no statement of what a successful response contains or what happens when html and text are both omitted, an agent still has open questions before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 38% across 8 parameters; cc, bcc, reply_to, subject, html and text carry no description in the schema and get no explanation here either. The only semantic hint is that "from" relates to the verified-domain constraint, which the schema's own example already illustrates. The description does almost nothing to compensate for the coverage gap.

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?

Specific verb plus resource ("Send one transactional email from a verified domain") with an explicit scope limit ("one", "Not for bulk or marketing email"). An agent immediately knows this is single-message transactional sending, distinct from the account-management siblings, though it never names an alternative send path.

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?

Provides a clear when-not exclusion ("Not for bulk or marketing email") and an implied prerequisite (verified domain on the account). It stops short of a full when/when-not/alternative matrix, but there is no sibling in this catalog that competes for the same task, so the guidance is adequate.

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