Obsidian Everywhere

by junnnnnw00

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Rename Note

rename_note

Destructive

Rename a note in place and automatically update all links pointing to it within Obsidian.

Instructions

Rename a note within its current folder and update links that point to it.

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>",
      "newName": "<newName>"
    },
    "name": "rename_note"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Existing note path, title, or alias.
`newName`	Yes	New filename only; use move_note to change folders.
`updateLinks`	No	Rewrite inbound links (default true).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true, so the tool is destructive. The description adds that it updates links, which is behavioral information beyond annotations. No contradiction; description aligns with destructive nature.

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?

Single concise sentence that is front-loaded with the primary action. No redundant information. Every word earns its place.

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

Completeness3/5

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

No output schema, but return values are typical for a rename operation. Description does not explain behavior when updateLinks is false or details about path resolution. Somewhat complete but could be richer for a mutation tool with destructive hint.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds extra meaning for 'newName' parameter: 'New filename only; use move_note to change folders.' This guides the agent on correct usage. Also clarifies updateLinks boolean. Adds value beyond schema.

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 it renames a note within its current folder and updates links. The verb 'rename' is specific, and the resource 'note' is unambiguous. The description distinguishes from sibling tools like move_note (which changes folder) and delete_note.

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 implies when to use this tool by stating 'within its current folder', contrasting with move_note for folder changes. However, it does not explicitly provide when-not or list alternatives. An agent would infer the usage context but lacks explicit guidance.

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