Skip to main content
Glama

get_note_attachment

Save a single note attachment as a file on this Mac and return its absolute path; images and text files are also returned inline. Requires user confirmation.

Instructions

Save one attachment of a note as a file on this Mac and return its absolute path. Images (JPEG, PNG, GIF, WebP, HEIC) are also returned as an image. PDF, text, RTF, DOC and DOCX files are also returned as text (cut at 100000 characters). Other types return the path only. Files above 25 MB are refused. Notes cannot save drawings, scans, tables and links: the call then fails with an error. Locked notes are not read. The file is kept for 24 hours. Give the attachment by 'name' or 'index' from get_note. Needs 'confirm' true on every call. Ask the user first, because the file is copied to ~/Library/Caches/applesauce/attachments.

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>"
    },
    "name": "get_note_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNote id from search_notes (it starts with x-coredata://).
nameNoAttachment name from get_note. Give 'name' or 'index', not both.
indexNoAttachment number from get_note. The first is 1.
confirmNoMust be true. Ask the user first: the call copies the attachment to this Mac.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations it discloses the 25 MB size cap, which content types fail (drawings, scans, tables, links), that locked notes are not read, the 100000-character text cut, the 24-hour file retention, and the cache directory the copy lands in. This is unusually rich operational context for a mutation tool.

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?

Front-loaded with the action and return value, then limitations, then preconditions. Every sentence carries distinct information and none repeats the schema verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description explains exactly what is returned for each type (path, image, text) and all failure modes an agent must anticipate, so nothing needed to call it correctly is missing.

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 the id/name/index/confirm meaning is already documented in the schema. The description reinforces the 'name or index' exclusivity and the confirm requirement but adds no format or edge-case detail beyond the structured fields, matching the baseline 3.

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 opening sentence names a specific verb and resource ('Save one attachment of a note as a file on this Mac') and states the return value ('its absolute path'), which cleanly separates it from get_note (reads note content) and get_mail_attachment (different source).

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?

It gives concrete preconditions: supply 'name' or 'index' from get_note, 'confirm' must be true on every call, and the user must be asked first. It does not explicitly state when not to use it or contrast it with the mail attachment sibling, so it falls short of a full 5.

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