Skip to main content
Glama

undo_move

Reverses the move of a note in the vault, restoring its prior path, rewritten links, and indexing record. Pass the note's current path to undo that move.

Instructions

Put a note the organizer moved back where it was. Pass the note's present path inside the vault; the latest move of that note is reversed, including the links that were rewritten and the note's indexing record.

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": {
      "path": "<path>"
    },
    "name": "undo_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful side effects: rewritten links are restored and the note's indexing record is updated as part of the reversal. That is exactly the kind of consequence an agent needs before invoking a mutation. It stops short of covering failure modes, such as behavior when no prior move exists, or whether the undo itself is reversible.

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, front-loaded with the action, followed by the parameter instruction and the side effects. No filler, no restatement of the tool name.

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 one-parameter mutation with no annotations and no output schema, the description covers purpose, argument meaning, and consequences. The remaining gap is edge-case behavior (no recorded move, stale path) which the agent would want before calling.

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 0% for the single parameter, so the description must compensate. It does add essential meaning by specifying the *present* path inside the vault rather than the original path, which is the one ambiguity an agent would otherwise hit. It does not describe path format, vault-relative syntax, or how to identify the note if its path is unknown.

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: put a moved note back where it was, and clarifies that only the latest move is reversed. The undo semantics are unambiguous and no sibling in the catalog performs this operation, so there is little risk of confusion, though the description never explicitly distinguishes itself from vault-organizing siblings like organize_vault.

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: 'the latest move of that note is reversed' signals a single-step undo, and the path guidance scopes it to notes the organizer moved. There is no explicit statement of when not to use it, what happens if the note was never moved, or what alternative to reach for if the move history is exhausted.

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