Skip to main content
Glama
Sign In
Another bloated Obsidian MCP Server

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

rename_note

Renames a note and updates all wikilinks that reference it, returning the count of notes with updated links.

Instructions

Rename a note and optionally update all wikilinks that reference it. Returns the count of notes with updated links.

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": {
      "oldPath": "<oldPath>",
      "newPath": "<newPath>"
    },
    "name": "rename_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
newPathYesNew path for the note (e.g., "Projects/NewName.md")
oldPathYesCurrent path of the note (e.g., "Projects/OldName.md")
updateLinksNoUpdate wikilinks in other notes that reference this note (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses the return value (count of updated links) and the optionality of link updates, but does not mention consequences of setting updateLinks to false (e.g., broken links) or any required permissions. It adds some value but leaves key behavioral gaps.

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 two concise sentences, front-loaded with the core action and immediately followed by the return value. Every word earns its place; there is no redundancy or filler.

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?

For a simple three-parameter tool with no output schema, the description covers the purpose, optional behavior, and return value. However, it omits caveats like the risk of broken links when updateLinks is false, and does not clarify whether the old path is fully replaced or if any validation occurs. Adequate but not comprehensive.

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 baseline 3 applies. The description adds context about wikilink updates and the returned count, but does not provide additional syntax or format details beyond the schema. It earns the baseline without exceeding it.

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 ('Rename') and resource ('a note'), and highlights the distinguishing feature of optionally updating wikilinks. This clearly separates it from sibling tools like move_note or update_note.

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?

The description implies usage when renaming a note while maintaining link references, but does not explicitly mention alternatives or exclusions (e.g., move_note for path changes without link updates). There is no explicit 'when not to use' guidance.

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

Deploy Server

Other Tools