Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

restore_note_version

Restore a note's title and content to a saved version while preserving the current text in history, so the change can be undone.

Instructions

Restore a note's title and content to a saved version. The current text is kept in history first, so this can be undone.

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": {
      "noteId": "<noteId>",
      "versionId": "<versionId>"
    },
    "name": "restore_note_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYes
versionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

The description earns credit for disclosing behavior beyond the annotations: the current text is snapshotted to history before overwriting, so the mutation is reversible. However, with destructiveHint=false and readOnlyHint=false already in the annotations, the remaining gaps (permissions required, what happens if versionId is stale, whether tags/metadata are also reverted) leave this at solid-but-partial.

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, and the reversibility guarantee is placed immediately after the action so the agent learns the risk profile up front.

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?

For a two-parameter mutation with annotations covering the safety profile, the description supplies the essential missing piece — that the overwrite is undoable via history. It is nearly complete; only the provenance of versionId and any permission prerequisite remain unaddressed.

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 0%, so the description carries the full burden for noteId and versionId. It only gestures at 'a saved version' and never explains where a versionId comes from, whether the ID is per-note, or what happens on an invalid pair — so the two required parameters are barely illuminated.

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 and resource plus scope: restoring a note's title and content to a saved version. That is clearly distinct from sibling restore_note (whole-note restore) and get_note_version (read-only), though it never explicitly names those siblings to sharpen 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 rather than stated — an agent can infer this is the write-side counterpart to get_note_version / list_note_versions. There is no explicit when-to-use, no exclusions, and no pointer telling the agent it must first obtain a versionId from a listing tool.

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