Skip to main content
Glama

graph_send_mail

Send emails via Microsoft Graph with CC/BCC, HTML or plain text bodies, importance levels, reply-to addresses, and shared mailbox support.

Instructions

Send an email.

A non-empty mailbox posts to /users/{mailbox}/sendMail, so the message is sent as that shared mailbox and needs the delegated Mail.Send.Shared permission.

Args: to: List of recipient email addresses. subject: Email subject. body: Email body content. When is_html is true, send explicit HTML; markdown is not converted. cc: Optional list of CC email addresses. bcc: Optional list of BCC email addresses. is_html: Whether to send the email body as HTML content (default: True). Use false for plain text. importance: Message importance: "low", "normal", or "high" (default "normal"). reply_to: Optional list of addresses that replies should be sent to. save_to_sent_items: Whether to keep a copy in Sent Items (default true). mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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": "graph_send_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
is_htmlNo
mailboxNo
subjectYes
reply_toNo
importanceNonormal
save_to_sent_itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the target endpoint, the required delegated Mail.Send.Shared permission, that markdown is not converted when is_html is true, and the defaults for save_to_sent_items and importance. It still omits that sending is irreversible (no recall) and says nothing about error or failure 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?

Front-loaded with the action, then organized as a readable Args list with the endpoint/permission context placed near the mailbox parameter it explains. Some lines merely echo the parameter name, and the endpoint discussion sits oddly inline after the first sentence, but there is little waste.

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 ten-parameter mutation tool with no annotations and no output schema, the definition covers purpose, parameters, defaults, and permission requirements adequately. Gaps remain around irreversibility, failure modes, and whether a sent-message identifier is returned, but nothing blocks correct invocation.

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 description coverage is 0%, so the Args block is the only source of parameter meaning, and it documents all ten parameters including defaults and accepted values for importance. A few entries are thin restatements ('cc: Optional list of CC email addresses'), but the important ones (body/is_html, mailbox) add real meaning beyond the schema.

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?

Opens with a specific verb+resource ('Send an email') and even names the Graph endpoint it hits, so the action is unambiguous. It never references sibling operations such as graph_create_mail_draft or graph_send_mail_draft, so an agent must infer the drafting alternative on its own.

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 rather than stated: nothing says when to send directly versus create/send a draft, or when to use graph_send_channel_message instead. The mailbox paragraph does provide a useful conditional ('A non-empty mailbox posts to /users/{mailbox}/sendMail'), which is closer to prerequisite guidance than to when-to-use guidance.

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