Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

outlook_download_task_attachment

Idempotent

Download a Microsoft To Do task attachment to a local file or return its content directly without writing to disk. Requires task and attachment IDs; limits downloads to 10 MB.

Instructions

Download a To Do task attachment to a local file, or return it with as_content=True.

save_path resolves inside the configured attachments directory; the write is atomic (temp file + replace), so a failed download never truncates a file already staged there. as_content writes nothing; 10 MB at most.

Input Schema

NameRequiredDescriptionDefault
list_idNo
task_idYes
save_pathNo
as_contentNo
attachment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 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 / list_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / list_id / default
      Removed value: -null
    • removedInput schema / properties / list_id / title
      Removed value: -"List Id"
    • addedInput schema / properties / list_id / type
      Added value: +"string"
    • 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 / properties / task_id / title
      Removed value: -"Task Id"
    • removedInput schema / title
      Removed value: -"outlook_download_task_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: -[
-  "task_id",
-  "attachment_id",
-  "save_path"
-]New value: +[
+  "task_id",
+  "attachment_id"
+]
  3. Addedv1.22.1

TDQS

A4.2/5.0
Behavior5/5

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

Beyond annotations, it discloses important behavior: `save_path` is constrained to the configured attachments directory, writes are atomic via temp-file-plus-replace, failed downloads do not truncate existing files, `as_content` writes nothing, and downloads are capped at 10 MB. These details materially improve safe invocation.

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 compact and front-loaded, stating the primary action first and then the important write-safety and size constraints. Every sentence adds useful information; nothing is redundant.

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 download tool with annotations and no output schema, it covers the main invocation modes, path behavior, atomicity, and size limit. The remaining gap is that it does not specify the exact form of the returned content when `as_content=True`, nor does it explain `list_id`.

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 carry parameter meaning. It adds strong semantics for `save_path` and `as_content`, but does not explain `list_id`, `task_id`, or `attachment_id`, leaving three of five parameters undocumented beyond their names.

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

Purpose5/5

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

The description states a specific verb and resource: download a To Do task attachment, with two retrieval modes. It distinguishes itself from generic attachment or task-listing siblings by naming the exact attachment type and the local-file versus content behavior.

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 clearly explains the two modes: default save-to-file and `as_content=True` for returning content. However, it does not explicitly say when to use this tool versus related siblings such as `outlook_list_task_attachments` or `outlook_download_attachment`, leaving selection context mostly inferable.

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