Skip to main content
Glama
outlook-mcp

outlook-mcp

by mpalermiti

outlook_download_task_attachment

Idempotent

Download a Microsoft To Do task attachment to a local file or retrieve its content directly, with a 10 MB limit and no overwriting of existing files.

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; it never replaces an existing file. as_content writes nothing; 10 MB at most.

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": {
      "task_id": "<task_id>",
      "attachment_id": "<attachment_id>"
    },
    "name": "outlook_download_task_attachment"
  }
}

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
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is partly covered; the description still adds real value: save_path is sandboxed to the configured attachments directory, existing files are never replaced, as_content performs no writes, and there is a 10 MB ceiling. It stops short of saying what happens on a collision (error vs. renamed file) or whether the directory is created if missing.

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?

Two tight sentences with the operation and its two modes front-loaded, then the constraints. Nothing is repeated from the schema or annotations and no clause is filler.

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 5-parameter tool with no output schema, the description covers the risky surface (path sandboxing, no overwrite, size cap, write-free content mode). Minor gaps remain around the ambiguity of list_id and the format of the returned content, which matters since there is no output schema to explain it.

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% across 5 parameters, so the description must compensate, and it does for the two non-obvious ones: save_path (resolved inside the attachments directory, non-overwriting) and as_content (no writes, returns content, 10 MB limit). list_id, task_id, and attachment_id are left unelaborated, and the exact form of the content returned (bytes, base64, or MIME) is unspecified.

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 opens with a precise verb+resource pair ('Download a To Do task attachment') and immediately states the two output modes, so an agent can distinguish it from the message-level sibling outlook_download_attachment. No reading of the schema is required to know what it does.

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 names the alternative mode ('or return it with `as_content=True`'), which is useful routing within the tool, but gives no guidance on when to prefer this over outlook_list_task_attachments (to discover attachments) or outlook_download_attachment (for mail attachments). Usage is implied rather than stated.

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