Skip to main content
Glama
sureshsankaran

Obsidian Tools MCP Server

rename_note

Change the name or location of an Obsidian note by specifying its current and new file paths.

Instructions

Rename or move a note to a new location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
oldPathYesCurrent path of the note
newPathYesNew path for the note

Implementation Reference

  • The handler function that executes the rename_note tool: resolves paths, validates existence, creates directories if needed, and renames the file using fs.rename.
    async function handleRenameNote(args: {
      oldPath: string;
      newPath: string;
    }): Promise<string> {
      const oldFullPath = resolvePath(args.oldPath);
      const newFullPath = resolvePath(args.newPath);
    
      if (!(await fileExists(oldFullPath))) {
        throw new Error(`Note not found at ${args.oldPath}`);
      }
    
      if (await fileExists(newFullPath)) {
        throw new Error(`Note already exists at ${args.newPath}`);
      }
    
      await ensureDir(newFullPath);
      await fs.rename(oldFullPath, newFullPath);
      return `Successfully moved note from ${args.oldPath} to ${args.newPath}`;
    }
  • Input schema for the rename_note tool, specifying oldPath and newPath as required string parameters.
    inputSchema: {
      type: "object",
      properties: {
        oldPath: {
          type: "string",
          description: "Current path of the note",
        },
        newPath: {
          type: "string",
          description: "New path for the note",
        },
      },
      required: ["oldPath", "newPath"],
    },
  • src/index.ts:131-148 (registration)
    Registration of the rename_note tool in the tools array, which is returned by list_tools.
    {
      name: "rename_note",
      description: "Rename or move a note to a new location",
      inputSchema: {
        type: "object",
        properties: {
          oldPath: {
            type: "string",
            description: "Current path of the note",
          },
          newPath: {
            type: "string",
            description: "New path for the note",
          },
        },
        required: ["oldPath", "newPath"],
      },
    },
  • src/index.ts:888-891 (registration)
    Registration of the handler in the main tool dispatch switch statement for call_tool requests.
    case "rename_note":
      result = await handleRenameNote(
        args as { oldPath: string; newPath: string }
      );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'rename or move' which implies mutation, but doesn't specify permissions needed, whether the operation is atomic, what happens on conflicts (e.g., if newPath exists), or error handling. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence with zero waste—it directly states the tool's function without redundancy. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

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

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain behavioral aspects like side effects, return values, or error conditions, leaving significant gaps for an AI agent to use it correctly.

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 schema description coverage is 100%, with clear descriptions for 'oldPath' and 'newPath'. The description adds no additional parameter semantics beyond what the schema provides, such as path format or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the tool's purpose with specific verbs ('rename or move') and resource ('a note'), distinguishing it from siblings like 'create_note', 'delete_note', or 'read_note'. However, it doesn't explicitly differentiate from 'update_note' which might also handle renaming, so it's not a perfect 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'update_note' or 'create_note' for similar operations. It lacks context on prerequisites, such as whether the note must exist or if the new path must be valid, leaving usage unclear.

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

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