Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by aniketbiswas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_file

Permanently delete a file from an Obsidian vault, with a mandatory confirmation step to prevent accidental data loss.

Instructions

Delete a file from the Obsidian vault. WARNING: This permanently removes the file. Use with caution.

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>",
      "confirm": "<confirm>"
    },
    "name": "delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the file to delete (relative to vault root).
confirmYesSet to true to confirm deletion. Required safety check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description clearly discloses the critical destructive behavior: 'WARNING: This permanently removes the file. Use with caution.' This is essential safety information. It does not, however, mention the confirmation requirement or any recovery options, but the warning sufficiently conveys the irreversible 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?

The description is extremely concise: two short sentences plus a warning. It is front-loaded with the action and immediately follows with the critical caution. Every word earns its place without redundancy.

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

Completeness4/5

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

For a simple two-parameter destructive tool with a complete schema, the description conveys the essential purpose and risk. It lacks clarification relative to sibling tools (e.g., 'delete_note') and does not state success/error behavior, but these are not required given the simplicity and schema completeness.

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% with both 'path' and 'confirm' fully described. The description adds no param-specific detail beyond what the schema already provides, so it defaults to the baseline. The warning about permanence indirectly supports the 'confirm' parameter but does not explain its syntax or semantics further.

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 states a specific verb and resource: 'Delete a file from the Obsidian vault.' This clearly identifies the action and target. However, it does not distinguish between deleting a file and the sibling 'delete_note' tool, leaving potential ambiguity about which is appropriate for different content types.

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 a warning about permanence but gives no guidance on when to use this tool versus alternatives like 'delete_note' or how to handle prerequisites (e.g., confirming paths). No specific usage context or exclusions are offered.

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