Skip to main content
Glama
Sign In
obsidian-mcp-server

obsidian-mcp-server

by indie-geeker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_note

Remove a note from your Obsidian vault by specifying its file path. Use this to clean up or eliminate unwanted notes.

Instructions

Delete a note from the vault

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": {
      "filepath": "<filepath>"
    },
    "name": "delete_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathYesPath to the note file to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Delete' implies a destructive, likely irreversible operation, but the description does not confirm irreversibility, permission requirements, or whether the note can be recovered. This is a significant gap for a destructive 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?

A single, front-loaded sentence with zero waste. Appropriate for a simple one-parameter tool.

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?

For a destructive, irreversible mutation with no annotations and no output schema, the description is too thin. It should disclose whether deletion is permanent, whether confirmation or specific permissions are required, and what happens on success or failure.

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 description coverage is 100%, with the single filepath parameter fully documented in the schema. The description adds no parameter detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (delete) and resource (a note from the vault). Clear and distinguishable from siblings like create_note or update_note, though it offers no explicit differentiation phrase beyond the obvious verb contrast.

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?

Provides no when-to-use context, no prerequisites, and no mention of alternatives. With destructive siblings like update_note present, guidance on when destruction is appropriate versus updating would be valuable, but none is 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