Skip to main content
Glama

Restore note version

restore_note_version

Put a note back to one of its earlier versions (from note_history). The text it has now is kept as a version too, so this can be undone the same way.

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": "<note>",
      "version": "<version>"
    },
    "name": "restore_note_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesThe note. Its id (from any other tool's output) or its exact title.
versionYesThe version id from note_history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is largely covered. The description adds genuinely useful behavior: the current text is preserved as a version, making the operation reversible in the same way. It does not address the non-idempotent hint or what happens if the version id is stale/invalid.

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?

Two compact sentences with no padding; the core action is front-loaded and the reversibility fact follows logically. Slightly more specification (e.g., what note_history returns that is needed) could be added without bloat.

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 no output schema and strong annotation coverage, the description supplies the essential missing pieces: the version source and the fact that the current text is retained. Missing only failure behavior and the meaning of non-idempotency, which are minor here.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents both parameters, including that note accepts an id or exact title and that version comes from note_history. The description's '(from note_history)' merely echoes the schema rather than adding syntax, format, or edge-case meaning. Baseline 3 applies.

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 ('Put a note back to one of its earlier versions') and ties the source to note_history, which implicitly separates it from the sibling restore_note (trash restore). It never explicitly contrasts the two, so an agent must infer that distinction from the sibling name alone.

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 parenthetical '(from note_history)' implies the version id must first be obtained via note_history, giving implicit ordering guidance. There is no explicit when-to-use versus restore_note/update_note statement and no stated prerequisites or exclusions.

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