Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

outlook_download_attachment

Idempotent

Download an Outlook email attachment to the configured attachments folder or return its content directly without writing a file, up to 10 MB.

Instructions

Download an attachment to save_path on the host, or return it with as_content=True.

save_path is resolved inside the configured attachments directory (attachments_dir, an attachments folder in the settings directory by default) — a bare filename lands there; a path outside it is refused. Same directory for reads and writes. as_content writes nothing; 10 MB at most.

Input Schema

NameRequiredDescriptionDefault
save_pathNo
as_contentNo
message_idYes
attachment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.30.2
    • removedInput schema / properties / as_content / title
      Removed value: -"As Content"
    • removedInput schema / properties / attachment_id / title
      Removed value: -"Attachment Id"
    • removedInput schema / properties / message_id / title
      Removed value: -"Message Id"
    • removedInput schema / properties / save_path / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / save_path / default
      Removed value: -null
    • removedInput schema / properties / save_path / title
      Removed value: -"Save Path"
    • addedInput schema / properties / save_path / type
      Added value: +"string"
    • removedInput schema / title
      Removed value: -"outlook_download_attachmentArguments"
  2. Changed5 schema fields changedv1.28.0
    • addedInput schema / properties / as_content
      Added value: +{
+  "default": false,
+  "title": "As Content",
+  "type": "boolean"
+}
    • addedInput schema / properties / save_path / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / save_path / default
      Added value: +null
    • removedInput schema / properties / save_path / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
-  "message_id",
-  "attachment_id",
-  "save_path"
-]New value: +[
+  "message_id",
+  "attachment_id"
+]
  3. First observedv1.11.0

TDQS

A3.9/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing path confinement behavior, refusal of paths outside the attachments directory, that reads and writes share the same directory, that as_content writes nothing, and the 10 MB size limit.

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?

The description is front-loaded, compact, and structured around the two main invocation modes. Every sentence adds useful operational detail without repetition.

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 tool with no output schema and zero schema parameter descriptions, the description covers the main file-path and content-return behavior but omits the meaning of the required message_id and attachment_id parameters and does not clarify the return shape when as_content is used.

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 0%, so the description must compensate. It meaningfully explains save_path and as_content semantics, but it does not explain the required message_id or attachment_id parameters.

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?

The description uses a clear verb and resource: download an attachment, either to save_path or returned as content. It is easy to understand, but it does not explicitly distinguish this from the sibling outlook_download_task_attachment.

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?

It explains the two operating modes (save to disk vs. return content) and when as_content avoids writing, but gives no explicit guidance on when to use this tool instead of related siblings such as outlook_list_attachments or outlook_download_task_attachment.

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