Skip to main content
Glama

Coline

Rewrite a note

update_note
DestructiveIdempotent

Rewrites a note: a new title, a new whole body (markdown), or both. Read it first and pass its revision so the person's newer edits are kept.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoThe whole new body in markdown.
titleNo
blocksNoColine's note blocks, instead of a markdown body. Rarely needed.
noteIdYesNote id from search, fetch or create_note.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
mutationIdNo
baseRevisionNoThe revision you read; edits made since then are merged, not lost.

Output Schema

NameRequiredDescriptionDefault
urlYes
bodyYes
titleYes
noteIdYes
revisionYes
bodyTruncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is carried structurally. The description adds meaningful context the annotations cannot: that the body is replaced wholesale, and that passing baseRevision merges concurrent edits rather than losing them. It does not cover permissions, the mutationId dedupe parameter, or what a stale/conflicting revision returns.

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 short sentences, zero filler. The replacement semantics come first and the read-then-write prerequisite follows, so the most decision-relevant information is front-loaded.

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?

An output schema exists and annotations cover safety, so the description only needs to carry the mutation semantics — which it does. Minor gaps remain around mutationId's purpose and whether blocks and body are mutually exclusive, both of which the description only gestures at ("instead of a markdown body" appears only in the schema).

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?

With 71% schema coverage the baseline is already moderate, and the description adds semantics for the two riskiest parameters: body is the whole replacement body in markdown, and baseRevision is the revision previously read, used for merge behavior. It leaves mutationId, workspace, noteId, and blocks entirely to the schema.

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 names a specific verb and resource ("Rewrites a note") and enumerates the mutable surface — title, whole markdown body, or both — which separates it from read/create siblings like get_note and create_note. It stops short of explicitly naming an alternative for partial edits, so it is clear but not fully differentiated.

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?

"Read it first and pass its revision" gives a concrete prerequisite and ordering (get_note, then update_note), which is real when-to-use guidance rather than an implied convention. It does not state when not to use it, e.g. for block-level tweaks versus a full rewrite.

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.

Resources