Skip to main content
Glama
maxkuminov

Obsidian MCP (pgvector + Ollama, self-hosted)

by maxkuminov
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

move_note

Move or rename a note in your vault while automatically updating internal references and backlinks. Optionally rewrite all incoming wikilinks to reflect the new path.

Instructions

Move or rename a note inside the vault. Requires a readwrite API key.

Updates notes_metadata.file_path for the moved note and note_links.target_path rows whose stored target matched the old path. Backlinks via target_note_id keep working without rewriting source notes (the moved note's id is unchanged).

With rewrite_links=True, also opens every source note that linked to this note and rewrites the link title in-place: [[Old]] → [[New]], [[Old|alias]] → [[New|alias]], [[Old#anchor]] → [[New#anchor]], ![[Old]] → ![[New]], and path-style [[folder/Old]] → [[new/folder/New]]. Aliases and anchors are preserved; only the title portion is rewritten.

Writes are atomic. See get_vault_guide for vault folder conventions.

Args: from_path: Vault-relative path of the existing note. to_path: Vault-relative path of the destination. Must not exist. Parent directories are created automatically. rewrite_links: If True, also rewrite incoming wikilinks and embeds in source notes. Off by default — opting in is destructive (it modifies other notes' bodies).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_pathYes
to_pathYes
rewrite_linksNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations provided, so description fully covers behavior: updates metadata, backlinks preserved, atomic writes, destructive rewrite_links behavior with examples of link rewriting. Discloses dependency on auth keys and modification of other notes.

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?

Well-structured: one-sentence summary, then detailed behavior, parameter explanations, and atomic guarantee. Each sentence adds value; no redundancy. Length justified by complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a complex tool: covers purpose, parameters, authentication, side effects (link rewriting), atomicity, and references external guide. Output schema exists so return values not required.

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

Parameters5/5

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

Schema coverage is 0%, but description adds detailed, clear semantics: from_path defined as vault-relative path, to_path requires non-existence and auto-creates parents, rewrite_links explained with examples and destructive warning. Fully compensates for lack of schema 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 clearly states the tool moves or renames a note inside the vault, with specific verb and resource. It distinguishes from sibling tools like create_note and delete_note by focusing on path changes.

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?

Provides clear context: requires readwrite API key, destination must not exist, parent directories auto-created. Mentions opting in for destructive rewrite_links. Refers to get_vault_guide for folder conventions. No explicit exclusion of alternatives but usage is well scoped.

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

This server cannot be installed

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/maxkuminov/obsidian-mcp'

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