Skip to main content
Glama

Update note

update_note
Idempotent

Change a note's title, body, or tags in your knowledge base; omitted fields remain unchanged.

Instructions

Change a note's title, body or tags. Fields left out stay as they are.

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": {
      "note_id": "<note_id>"
    },
    "name": "update_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoReplaces the whole body
tagsNoReplaces the whole tag set
titleNo
note_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
uriYesResource URI for this note
urlNoSet for bookmarks
bodyYes
tagsYes
titleYes
created_atYes
updated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false and idempotent=true, so the safety profile is covered. The description adds one genuinely useful behavior — omitted fields are preserved (partial update) — but leaves open whether passing null explicitly clears a field or is treated as omission, given every property defaults to null in the schema.

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?

Two sentences, zero filler, with the resource and mutable fields front-loaded and the partial-update rule in the second position where it is needed most.

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?

With rich annotations and an output schema, the description covers purpose and update semantics adequately for a small 4-parameter tool. It does not say what happens when note_id does not exist, nor whether tags are validated, but these are modest gaps against the structured coverage already present.

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?

At 50% schema coverage the description must compensate, and it does: it names the three mutable fields (title, body, tags) and, more importantly, states that fields left out retain their current values, which disambiguates the null defaults. note_id is not addressed but is required and obvious from context.

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?

"Change a note's title, body or tags" gives a specific verb plus resource and enumerates the mutable fields, which cleanly separates it from add_note, delete_note and get_note. It stops short of naming a sibling or contrast case, but the action itself is unambiguous.

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 second sentence implies patch-style editing rather than replacement, which helps an agent decide how to call it, but there is no explicit statement of when to choose this over save_bookmark or add_note, and no preconditions (e.g. the note must already exist).

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