Skip to main content
Glama

append_to_note

Add plain text as a new paragraph at the end of a note; locked notes remain unchanged, but rewriting the note can alter rich content such as drawings.

Instructions

Add plain text as a new paragraph at the end of a note. Notes writes the whole note again, so some rich content (for example a drawing) can change. Locked notes are not changed.

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

Input Schema

NameRequiredDescriptionDefault
idYesNote id from search_notes (it starts with x-coredata://).
textYesPlain text to add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare readOnly=false, openWorld=false, destructiveHint=false, and the description goes further by warning that the whole note is rewritten and rich content such as a drawing can change, plus that locked notes are silently skipped. That is valuable non-obvious behavioral context. However, the rewrite side effect is arguably close to destructive and no return value or confirmation behavior is described, so it is strong but not exhaustive.

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 sentences, purpose front-loaded, each conveying a distinct fact (action, side effect, locked-note behavior). The sentence 'Notes writes the whole note again' is slightly awkward but not wasteful.

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-required-parameter tool with no output schema, the description covers the action, the reconstruction side effect, and the locked-note no-op. Only the return/confirmation behavior and the choice against update_note are left unstated.

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 both parameters are already documented in the schema, including the id format (x-coredata://). The description's 'plain text' phrasing reinforces that rich text is not accepted, which is slightly additive but largely overlaps the schema text 'Plain text to add.' Baseline 3 applies.

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 states a specific verb (add), resource (note), and precise placement (new paragraph at the end). It clearly separates append semantics from a generic rewrite, though it never names update_note as the alternative for whole-note edits.

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 implied by the append-at-end framing rather than stated: an agent can infer this is for adding trailing text, not for editing existing content. No explicit when-not guidance or named alternative (e.g., update_note) is given, though the locked-note caveat is a useful condition.

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