Skip to main content
Glama

Coline

Save a doc's edits

save_doc
Idempotent

Saves the person's edits from the doc editor in the chat against 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>",
      "docId": "<docId>",
      "title": "<title>",
      "content": "<content>",
      "layout": "<layout>",
      "baseRevision": "<baseRevision>",
      "mutationId": "<mutationId>"
    },
    "name": "save_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
docIdYesDoc id from search, fetch or create_doc.
titleYes
layoutYes
contentYesThe paged document as Coline's editor holds it.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the valuable behavioral detail that the save is anchored to a starting revision, implying conflict/staleness semantics, but it never says what happens on a revision mismatch, whether the save overwrites or rejects, or how mutationId relates to idempotency.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though arguably under-sized for a 7-parameter mutation tool with nested objects.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. But for a 7-required-parameter write tool with nested content/layout objects and a revision-conflict model, the description omits parameter guidance and conflict behavior.

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 43% across 7 required parameters; layout, title, baseRevision and mutationId carry no schema description. The description only gestures at baseRevision ('the revision they started from') and says nothing about mutationId, content, or layout, so it does not compensate for the coverage gap.

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?

States a specific verb+resource ('Saves ... edits from the doc editor') and adds scope ('in the chat') plus the concurrency framing ('against the revision they started from'). It does not, however, distinguish itself from the overlapping siblings create_doc, update_doc, or save_note, leaving the agent to infer the boundary.

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?

Usage is implied by 'from the doc editor in the chat' — the agent can infer this is called after editing in the chat editor. There is no explicit when-to-use versus update_doc, no statement of what happens if the doc was never opened, and no when-not guidance.

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