Skip to main content
Glama

Add attachment

add_attachment

Attach a file to an existing Outlook draft, event, or contact by ID, using a local path, base64 content, or plain text.

Instructions

Attach a file to a draft (or to an event/contact you own).

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": {
      "id": "<id>",
      "attachment": "<attachment>"
    },
    "name": "add_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDraft, event or contact ID
attachmentYesExactly one of path, contentBase64 or text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description need not restate it. The description adds the ownership scoping constraint (a genuine behavioral fact not in the annotations), which is a modest but real addition. It says nothing about size limits, failure modes for bad paths, or what happens to the target draft/event, so the addition is thin.

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 short sentence with the target scope front-loaded and zero filler. It is arguably a touch too terse for a mutation tool, but nothing is wasted.

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?

With rich nested-object schema documentation and mutation annotations present, the description covers the minimum: what is attached and to what. It remains vague on what 'you own' means operationally and on the expected outcome of a successful attach, which is a gap for a write tool with no output schema.

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 100%, so 'id', 'path', 'text', 'contentBase64', 'name' and 'contentType' are all already documented in the schema, including the 'exactly one of path, contentBase64 or text' rule. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 states a specific verb and resource ('Attach a file') plus the target scope ('a draft ... or an event/contact'). An agent can tell it apart from list_attachments, download_attachment and remove_attachment by the verb alone, though no sibling is named explicitly.

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?

The parenthetical 'or to an event/contact you own' implies a permission prerequisite and target selection, which is real usage context. However, there is no explicit when-to-use-vs-alternative routing (e.g., why attach here versus creating a draft with the file), and the ownership constraint is left unqualified.

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