Skip to main content
Glama

Delete Note

vault_delete_note
Destructive

Permanently delete a markdown note from disk. The file is removed directly without undo; protected paths are blocked to prevent accidental loss of memory or daily notes.

Instructions

Permanently delete a markdown note. The note is removed from disk directly (not moved to a trash folder), and this server has no undo — recovery depends on your own backups or sync history. After deletion it no longer appears in search results or backlinks, and links to it from other notes become broken (detectable via vault_get_outgoing_links). Protected paths (About Me/, Daily Notes/) are refused to prevent accidental loss of memory or daily notes.

Example: vault_delete_note({ path: "Scratch/temp.md" })

When to use: Removing a note you no longer need. Prefer vault_delete_memory for removing individual dated entries from About Me/ memory files.

Errors:

  • "cannot delete protected path …" — the path sits under a protected folder; use vault_delete_memory for memory entries

  • "path traversal blocked" — path escapes the vault root; use a vault-relative path

  • note does not exist — verify the path with vault_list_notes before deleting

Returns: Confirmation message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesVault-relative path of the note to delete
Behavior5/5

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

Description details that the note is removed from disk, no undo, recovery depends on backups, and that deletion breaks backlinks and removes from search. This adds context beyond the destructiveHint annotation.

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?

Well-structured: key behavior, example, usage guidance, error cases. Every sentence is informative and no redundancy.

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

Completeness5/5

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

Covers all aspects: purpose, when/what to use, alternatives, effects on system (broken links, search), protected paths, error handling. No output schema needed given return is a confirmation message described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a description. The description adds an example, specifies vault-relative path, and explains error conditions related to path (protected, traversal, does not exist).

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 clearly states the tool permanently deletes a markdown note, directly from disk, with no undo. It distinguishes from vault_delete_memory by specifying that tool is for memory entries in About Me/ files.

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

Usage Guidelines5/5

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

Explicitly states 'When to use: Removing a note you no longer need' and 'Prefer vault_delete_memory for removing individual dated entries from About Me/ memory files.' Also explains protected paths and prerequisites like verifying path with vault_list_notes.

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/aliasunder/vault-cortex'

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