Skip to main content
Glama

Coline

Save a note's edits

save_note
Idempotent

Saves the person's edits from the note editor in the chat, merged with any newer edits since the revision they started from.

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>",
      "title": "<title>",
      "blocks": "<blocks>",
      "baseRevision": "<baseRevision>",
      "mutationId": "<mutationId>"
    },
    "name": "save_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
blocksYes
noteIdYesNote id from search, fetch or create_note.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
mutationIdYes
baseRevisionYes

Output Schema

NameRequiredDescriptionDefault
revisionYes
updatedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already disclose that this is a non-read-only, non-destructive, idempotent operation. The description adds meaningful behavior beyond that: saves are merged with newer edits made since the caller's base revision, which communicates optimistic-concurrency semantics. It still omits what happens on conflicts, what requires authorization, and how mutationId affects idempotency.

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?

The definition is a single front-loaded sentence with no filler. It states the action first and then the merge behavior, so every phrase contributes to the agent's understanding.

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

Completeness3/5

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

The tool has six required parameters, a low schema description coverage, and no explicit sibling differentiation. The description covers the core save-and-merge behavior, and the output schema and annotations reduce the need to explain return values and safety. However, key parameter semantics and the choice between save_note and update_note remain unexplained, making the definition only minimally complete for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, with workspace and noteId documented in the schema and title, blocks, baseRevision, and mutationId left without descriptions. The description gives some conceptual meaning to baseRevision through 'the revision they started from,' but it does not explain mutationId, the expected block structure, or the roles of the remaining undocumented parameters. This does not sufficiently compensate for the low schema coverage.

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 and resource: it saves a person's edits to a note from the chat-based editor. It also names the merge behavior, but it does not distinguish this tool from siblings such as update_note or create_note, so the purpose is clear without being 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'from the note editor in the chat' implies the intended invocation context, but the description gives no explicit when-to-use versus when-not-to-use guidance. It never names update_note or another alternative, so the agent must infer the routing.

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