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

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

restore_backup

Recover a note from a backup file. Optionally back up the current note before restoring to prevent data loss.

Instructions

Restore a note from a backup. Optionally creates a backup of current content first.

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": {
      "backupPath": "<backupPath>"
    },
    "name": "restore_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
backupPathYesPath to the backup file to restore
targetPathNoTarget path for restored note (defaults to original location)
createBackupFirstNoCreate a backup of current note before restoring (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It hints at destructiveness by mentioning the optional backup creation, implying that restoration may overwrite current content. However, it does not explicitly state overwrite semantics, targetPath behavior, or failure conditions, leaving a transparency gap.

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 sentences, front-loaded with the primary action and a key optional behavior. Every word earns its place with no filler or redundancy.

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?

The description covers the core action and the optional backup feature, but it omits return values, error scenarios, and the effect of targetPath. With no output schema and no annotations, the description should provide more context to be fully complete for a mutation tool.

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 already provides 100% description coverage for all three parameters, so the description needs minimal param info. The phrase 'Optionally creates a backup of current content first' aligns with createBackupFirst but adds no new meaning beyond the schema defaults and 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 opens with 'Restore a note from a backup', a specific verb+resource that clearly identifies the action. It distinguishes itself from sibling tools like create_note_backup and list_backups, which serve different purposes.

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 provides clear context for when to use the tool, especially the optional backup-first behavior ('Optionally creates a backup of current content first'). It does not explicitly exclude alternatives or list when-not-to-use, but the restore purpose is unambiguous and distinct from the sibling tools.

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