Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

export_notes

Read-only

Download a ZIP backup of all notes in readable Markdown or Anchor’s re-import format, saved to disk without overwriting and returning the file path.

Instructions

Download a zip backup of all the user's notes. markdown = readable .md files; anchor = Anchor's own format, for re-importing. Saved to disk (never overwriting); returns the path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoDefault markdown
saveToNoFolder or file path; default is the user's Downloads folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Adds useful behavior beyond the annotations: the 'never overwriting' guarantee and 'returns the path' outcome. However, it does not reconcile that writing files to local disk is a side effect on the user's machine even though readOnlyHint is true, and it says nothing about size limits, progress, or failure modes for a bulk export.

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?

Three short, front-loaded clauses: what it does, format meanings, and save/return behavior. No filler.

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?

Two optional parameters, no output schema, and the description covers both formats, the on-disk write semantics, no-overwrite behavior, and the return value. Only the exact scope of 'all the user's notes' (workspaces, trash, shares) is left ambiguous.

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 100%, so baseline is 3; the description earns above baseline by explaining why the two enum values exist — markdown for readable files, anchor for re-importing — which the schema does not convey. The saveTo parameter is left to the schema, which is acceptable.

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?

A specific verb (download/export) and resource (all of the user's notes) with a stated artifact type (zip backup). It is clearly distinguishable from per-note siblings like get_note or search_notes, 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 'for re-importing' note on the anchor format implies the backup/round-trip use case, but there is no explicit when-to-use or when-not guidance, no statement about scope limits (e.g., all notes vs. shared/trashed notes), and no prerequisites.

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