Skip to main content
Glama

Outlook Send Mail

outlook_send_mail
Destructive

Sends a new email through the running Outlook profile, with optional CC and a confirmation flag required because the action cannot be undone.

Instructions

Send a new email through the running Outlook profile. This cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bodyYes
confirmNoMust be true to run this write or destructive tool.
subjectYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so "cannot be undone" largely restates them. The one genuinely additive fact is that sending goes through the running Outlook profile, implying the authenticated desktop session rather than separate credentials — useful, but no mention of confirm gating, attachment limits, 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?

Two short sentences, front-loaded with the action and the irreversibility warning, with no filler. Nothing wasted, though there is also little substance.

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?

The output schema covers return values, so the description need not explain results. However, for a destructive 5-parameter tool it omits the confirm prerequisite and all recipient/content parameter semantics, which are exactly the gaps the schema does not fill.

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 description coverage is only 20% (just confirm), and the description adds no meaning for to, cc, subject, or body — no format expectations, recipient syntax, or plain-vs-HTML body guidance. For a destructive tool with mostly undocumented parameters, this leaves the agent guessing.

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") and the qualifier "new" differentiates it from the drafting/reply sibling. It does not explicitly name an alternative, but an agent can tell what it does 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 Guidelines2/5

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

No when-to-use or when-not-to-use guidance: nothing tells the agent to prefer outlook_draft_reply when a review step is wanted, and it never mentions that the required confirm flag must be set to true before the call can succeed.

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