Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

append_to_note

Add markdown to the end of a note while preserving its existing content and formatting. Use it to extend notes with headings, lists, links, or code blocks without rewriting them.

Instructions

Add markdown to the end of a note without touching its existing content or formatting.

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

Input Schema

NameRequiredDescriptionDefault
idYes
contentYesMarkdown. Supported: # headings (1-3), **bold**, *italic*, <u>underline</u>, ~~strike~~, ==highlight==, [links](url), - bullets, 1. numbered, - [ ] / - [x] checklists (nest with 4 spaces), > quotes, ``` code blocks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive write (readOnlyHint=false, destructiveHint=false), and the description reinforces that with the 'without touching existing content or formatting' guarantee, which is genuine added context. It does not say what is returned, whether the note must be untrashed/unlocked, or what permissions or failure modes apply.

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?

One front-loaded sentence that names the action, the target location, and the key guarantee with zero filler.

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?

For a simple two-parameter append, the description covers the essential behavior and, aided by annotations, the safety profile. With no output schema and an undescribed id parameter, it leaves the agent guessing about the identifier and the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the content parameter is richly documented in the schema while the id parameter has no description at all. The description mentions markdown and that the target is a note, but adds no detail on id format or constraints, so the undocumented parameter stays undocumented.

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 (add/append markdown) on a specific resource (a note) with a precise location (the end). It implicitly separates itself from update_note by promising existing content and formatting survive, though it never names that sibling.

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?

Usage is only implied: the 'without touching its existing content' clause signals when to prefer this over a general update, but there is no explicit when-to-use/when-not-to-use statement and no mention of alternatives such as update_note.

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