Skip to main content
Glama

Save an email attachment to OneDrive

save_outlook_attachment_to_onedrive

Copy one attachment of an Outlook message into this account's OneDrive, as-is — any file type, up to 10 MB, without reading it. Goes into the folder parentItemId (from list_onedrive_items or search_onedrive_items) or the drive root when omitted; the name defaults to the attachment's own, and a taken name gets a suffix rather than overwriting. Get attachmentId from get_outlook_message.

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": {
      "mailbox": "<mailbox>",
      "messageId": "<messageId>",
      "attachmentId": "<attachmentId>"
    },
    "name": "save_outlook_attachment_to_onedrive"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFile name to save under; defaults to the attachment's name
mailboxYesEmail address of the connected Outlook/Microsoft 365 mailbox to act on. Call list_authorized_mailboxes to see available options.
messageIdYes
attachmentIdYes
parentItemIdNoDestination folder id; omit for the drive root

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-readOnly and non-destructive, and the description adds genuinely new behavior: a 10 MB cap, file-type agnostic, byte-for-byte 'as-is' saving without reading, and name-collision handling that adds a suffix instead of overwriting. It omits auth/permission requirements and any return information, keeping it below 5.

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?

A single dense paragraph that front-loads the core action and then layers destination, naming, and ID provenance. Every clause carries information, though the sentential packing makes it slightly heavier to parse than a two-sentence split would be.

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?

With no output schema and a 5-parameter mutation, the description covers the destination, naming, size limit, and ID sources an agent needs to invoke it correctly. The only meaningful omission is what the call returns on success.

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 coverage is 60%, and the description compensates by explaining parentItemId's default (drive root) and sourcing, the name default (attachment's own name), and where attachmentId comes from. mailbox and messageId are left to the schema/obvious context, leaving a small residual gap.

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 (copy), a specific resource (one email attachment), and both endpoints (Outlook message -> this account's OneDrive), which cleanly separates it from read_outlook_attachment, save_gmail_attachment_to_drive, and move_onedrive_item.

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 destination resolution path (parentItemId from list_onedrive_items/search_onedrive_items, or drive root when omitted) and points to get_outlook_message for attachmentId, giving an agent a clear recipe. It does not explicitly state when to prefer this over reading the attachment first or moving an existing OneDrive item, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources