Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

add_attachment

Attach a local image or audio file up to 50 MB to an existing Anchor note using its note ID and absolute file path. Supports .jpg, .png, .webp, .gif, .mp3, .wav, and other media formats.

Instructions

Attach a local file to a note. Anchor accepts images and audio up to 50 MB (.jpg .jpeg .png .webp .gif .mp3 .wav .m4a .mp4 .ogg .aac .weba .webm).

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

Input Schema

NameRequiredDescriptionDefault
noteIdYes
filePathYesAbsolute path of the local file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive, non-open-world write, so the bar is lower; the description still adds real value with a 50 MB size cap and an explicit list of accepted extensions/formats. It does not cover failure behavior, duplicate handling, or whether the upload is atomic, which keeps it from a 5.

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?

Two tight sentences, front-loaded with the core action and followed by the constraining details. No filler or restated title.

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 simple two-parameter tool with no output schema and clear annotations, the description covers purpose plus the practical constraints that matter for a file upload. The remaining gap is what the call returns and how failures or duplicate filenames are handled.

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?

With only 50% schema coverage (noteId is undocumented), the description compensates by constraining filePath to a local file and enumerating valid formats and size. It does not clarify noteId's expected format (id vs. path vs. slug), leaving one parameter under-explained.

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 uses a specific verb and resource ("Attach a local file to a note"), which is clearly distinct from text-oriented siblings like append_to_note and create_note. It stops short of naming any sibling explicitly, so the differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus append_to_note, create_note, or other write tools, and no prerequisites are given (e.g., that noteId must reference an existing note). The reader must infer usage entirely from the one-line purpose.

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