Skip to main content
Glama

Send Email

send_message
Destructive

Send a new email with recipient addresses, subject, body, and optional shared mailbox or HTML content type via Microsoft 365.

Instructions

Send a new email message

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

Input Schema

NameRequiredDescriptionDefault
toYesRecipient email address(es), comma-separated for multiple
bodyYesEmail body content
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
subjectYesEmail subject
content_typeNoBody content type: Text or HTML (default: Text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known without the description; the bar is lower but no credit is earned. The description adds nothing about the immediate, irreversible nature of a send, whether the message appears in Sent Items, or what happens if a delegated mailbox is required but omitted. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, front-loaded and free of padding, but the brevity comes from under-specification rather than disciplined compression. There is no wasted word, yet the one sentence barely earns its place.

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?

For a five-parameter destructive send operation, the description leaves the agent reliant on the schema and annotations, both of which are complete here (full param docs, explicit destructive hint, no output schema needed). The remaining gap is disambiguation from the many sibling send/create-draft tools, which the description does not address.

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 all five parameters including the delegated-mailbox and content_type nuances are already documented in the schema. The description adds no parameter meaning at all, which lands at the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Send a new email message" states a verb and a resource, so the basic purpose is legible, but it adds essentially nothing beyond the title "Send Email." It does not distinguish this tool from send_draft, send_reply, send_forward, or send_channel_message/send_chat_message, which an agent must choose between.

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?

There is no when-to-use guidance, no exclusion of alternatives (drafts, replies, forwards, other channels), and no note about prerequisites such as delegated mailbox configuration. The agent must infer everything from sibling names.

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