Skip to main content
Glama

update_note

Destructive

Change a note's title, plain-text body, or both; returns previous title and body so edits can be undone. Locked notes remain unchanged.

Instructions

Change the title or the plain text body of a note. Give 'title', 'body' or both. 'body' replaces the whole body, and the title stays as the first line (a heading). 'title' alone renames the note and keeps the rest. The result has 'previous_title' and 'previous_body' (the old text below the title), so the change can be undone with this tool. Notes writes the whole note again, so rich content (for example a drawing, a table or formatting) 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>"
    },
    "name": "update_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNote id from search_notes (it starts with x-coredata://).
bodyNoNew plain text body. It replaces the whole body. Line breaks are kept.
titleNoNew title, on one line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations by warning that the whole note is rewritten, so rich content such as drawings, tables or formatting can change, and that locked notes are skipped. It also documents the returned previous_title/previous_body, which explains how the destructive change can be undone.

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?

Front-loaded with the core action, then behavior, then the return and the lock caveat. Dense but every sentence carries information; a couple of clauses ('the old text below the title', 'Notes writes the whole note again') could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation tool with no output schema, it covers input combinations, destructive side effects, the returned undo data, and the locked-note edge case. Nothing an agent needs in order to call it safely is missing.

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 the baseline is 3, but the description adds genuine meaning: title is the one-line heading, body replaces everything below it, and title-alone is a rename that preserves the rest. The interaction between the two optional parameters is exactly what the schema cannot express.

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?

Names a specific verb and resource ('Change the title or the plain text body of a note') and immediately clarifies the scope: title, body, or both. The replacement semantics distinguish it from an append-style sibling, but it never names an alternative explicitly.

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?

Clearly states the accepted combinations ('Give title, body or both') and what each does, plus the exclusion that locked notes are not changed. It stops short of routing the agent to append_to_note for additive edits, leaving that inference to the reader.

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