Skip to main content
Glama

Append Note

append_note

The default way to add to an existing note: use when the user adds an item to a list they keep, records another decision, or extends a running log. Additive — existing content is preserved. Call list_notes first to find the right note id by its title and preview. Fails cleanly if the note is set to read-only for AI assistants.

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_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe note id to append to
contentYesContent to append (a separating newline is added when needed)

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
sourceYes
contentYes
created_atYes
updated_atYes
agent_accessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, but the description adds real value beyond them: it says existing content is preserved and that the call fails cleanly when the note is read-only for AI assistants. It does not discuss repeat-append behavior despite non-idempotency, but the safety profile is well covered.

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?

Four short sentences, front-loaded with the core purpose and default status, then behavior, then prerequisite, then failure mode. No sentence is redundant.

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 two-parameter append tool with full schema coverage, annotations, and an output schema, the description covers purpose, prerequisites, and the main failure mode. The only minor gap is that it says nothing about repeated appends or ordering, which matters slightly given non-idempotency.

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% and already documents both fields, including the newline behavior, so the baseline is 3. The description adds a bit more by explaining how to source the id ('by its title and preview' via list_notes), which the schema does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('add to an existing note') and immediately qualifies it as 'the default way' and 'additive', which separates it from create_note and update_note in the sibling set. An agent can identify the operation without opening the schema.

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 three concrete trigger scenarios (adding a list item, recording another decision, extending a log) and a prerequisite step ('Call list_notes first to find the right note id'). It stops short of an explicit when-not-to-use or a named alternative for replacing content, so it falls just below the top mark.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.