Obsidian Everywhere

Overview Schema Source Related Servers Discussions Admin

Move Note

move_note

Destructive

Move a note to a new vault-relative path and update all wikilinks and Markdown links pointing to it. Fails if destination exists.

Instructions

Move a note to a new vault-relative path and update every resolvable wikilink/Markdown link that pointed to it. Fails if the destination exists.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "move_note"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	New vault-relative path; .md is added automatically.
`from`	Yes	Existing note path, title, or alias.
`updateLinks`	No	Rewrite inbound links (default true).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Description adds crucial behaviors beyond annotations: link updating and failure condition. Annotations say destructiveHint=true but no further details. Description fills gap with concrete side effects.

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 waste. Each sentence conveys essential information: action, side effect, and constraint. Front-loaded with verb and resource.

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?

Covers purpose, key behavior, and failure case. Missing prerequisites (e.g., note must exist) and return value. Given no output schema, description could mention success signal. Still fairly complete for a mutation tool with good annotations.

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%, so description adds little beyond schema. It restates 'vault-relative' path and link update behavior, but doesn't clarify parameter types or defaults more than the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Move), resource (note), and key behaviors (update links, fails if destination exists). It distinguishes from sibling tools like rename_note by specifying path change and link updating.

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?

Only implicit usage context: fails on destination exists. No explicit when-to-use, when-not-to-use, or alternatives (e.g., rename_note for just renaming). Sibling tools exist but no guidance.

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