Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

get_attachment

Read-onlyIdempotent

Reads an Outlook attachment stored locally, extracting readable text, returning its file path, or opening it; reports when the file is missing and preserves orphaned attachment text.

Instructions

Read an attachment from local storage. Never downloads from a server: if the file is not on this Mac, the result says so. Ids like 'orphan:12' are files that no archived message owns: their text stays available even after Outlook deletes the file.

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

Input Schema

NameRequiredDescriptionDefault
modeNotext: extract readable text (PDF, Word, Excel, plain text, CSV, calendar); path: return a local file path; open: open the file in its default Mac apptext
offsetNoText character offset, for paging long text
max_charsNo
attachment_idYesattachment_id from list_attachments, or an id like 'orphan:12' from search_files

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the description's job is to add behavior beyond that — and it does: no network fetch, graceful 'not found locally' reporting, and the durability note that orphan attachments' text survives Outlook deleting the file. It does not cover what 'open' mode does as a side effect or anything about size limits.

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?

Three short sentences, front-loaded with the core action and the no-download rule. The orphan-id sentence is longer but carries non-obvious information, so little is wasted.

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 4-parameter read tool with no output schema, the description covers the main risk (missing local file) and the id provenance. The remaining gap — how the result differs across text/path/open modes and what paging output looks like — is minor given the schema's enum documentation.

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 coverage is 75%, with the mode enum, offset and attachment_id already documented in the schema; max_chars has no description. The description adds real meaning only for orphan ids (no owning archived message, text persists), and says nothing about mode='path' vs 'open' behavior beyond what the schema states. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Read an attachment from local storage') plus the key scope constraint (local only, never a server download). The orphan-id explanation further pins down what kinds of identifiers it accepts, so an agent can tell this apart from list_attachments or search_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explains the condition under which it fails ('if the file is not on this Mac, the result says so') and indicates where ids come from ('attachment_id from list_attachments, or an id like orphan:12 from search_files'). It does not explicitly say when to prefer it over those siblings, but the sourcing hints cover most selection cases.

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