Skip to main content
Glama
noragami90

obsidian-connector

by noragami90

Move or rename note

move_note

Move or rename a note in your Obsidian vault, automatically updating all wikilinks in other notes that reference it.

Instructions

Move or rename a note and rewrite [[wikilinks]] in other notes that point to it. Refuses to overwrite an existing file unless 'overwrite' is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesNew vault-relative path
fromYesCurrent vault-relative path
overwriteNoAllow replacing an existing file at the destination (default: false)
update_linksNoRewrite backlinks in other notes (default: true)
Behavior4/5

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

The description discloses the key side effect of rewriting wikilinks and the refusal behavior for overwriting. Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds context beyond those flags. No contradiction.

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?

The description is extremely concise, using two sentences to convey the core action and a key constraint. No unnecessary words, front-loaded with the main purpose.

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?

Given the tool's simplicity and the absence of an output schema, the description covers essential behavior: move/rename, link rewriting, and overwrite refusal. It is complete enough for an agent to understand the tool's effects.

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?

The input schema covers all 4 parameters with descriptions, achieving 100% coverage. The description adds little extra parameter-level meaning beyond restating the overwrite behavior. Baseline 3 is appropriate.

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 clearly specifies the verb (move/rename) and resource (note), and uniquely highlights the rewriting of [[wikilinks]] in other notes. This distinguishes it from sibling tools like delete_note or edit_note, which have different functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates when to use this tool (to move or rename a note) and provides a critical behavioral condition (refusing to overwrite unless 'overwrite' is true). However, it does not explicitly name alternatives or state when not to use it, which would strengthen guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/noragami90/obsidian-connector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server