Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

get_attachment

Read-only

Retrieve an attachment from an Anchor note. Small images are displayed directly, while audio and large images are saved to disk without overwriting and the file path is returned.

Instructions

Get an attachment. Images up to 3.5 MB are shown to you directly; audio and larger images are saved to disk (never overwriting) and the path is returned. Pass saveTo to always save.

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

Input Schema

NameRequiredDescriptionDefault
noteIdYes
saveToNoFolder or file path; default is the user's Downloads folder
attachmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses the 3.5 MB threshold, that images are surfaced inline, that audio and oversized images are persisted to disk, that files are never overwritten, and that a path is returned. This is exactly the behavioral context annotations can't carry.

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, front-loaded sentences with no filler; the size threshold and save behavior come first, with the escape hatch (`saveTo`) last. Tight and readable.

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, the description correctly explains what is returned (inline content vs. a file path) and where it lands, which is what an agent needs to interpret the result. Minor gap in describing edge cases like attachment-not-found or disk errors.

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 33%, with only `saveTo` documented in the schema. The description reinforces saveTo's effect ('always save') but adds nothing about noteId or attachmentId. The two undocumented IDs are largely self-evident, keeping this at a baseline 3.

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?

States a specific verb and resource ('Get an attachment') and immediately characterizes the retrieval semantics (inline vs. saved to disk). It is distinguishable from siblings like list_attachments and add_attachment, though it doesn't name them.

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?

Gives clear conditional usage: large images/audio go to disk automatically, and 'Pass `saveTo` to always save' tells the agent when to use the optional parameter. It stops short of explicit when-not guidance or naming alternatives.

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