NoteDiscovery MCP Server

delete_folder

Deletes an empty folder from the vault and rejects requests when the folder contains items or is the vault root, preventing accidental data loss.

Instructions

Delete an empty folder. Fails if the folder still has anything in it, or if it is the vault root.

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

Input Schema

Name	Required	Description	Default
`path`	Yes	Path of the folder to delete

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.34.1Nov 13, 2026

TDQS

A3.8/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 full behavioral burden. It does disclose the two failure conditions, which is valuable, but it says nothing about irreversibility, whether a confirmation step is needed, or what happens on success — all material for a destructive operation.

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?

Two short sentences with zero filler, and the core action is front-loaded before the constraints. Every clause earns its place.

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 one-parameter destructive tool with no annotations and no output schema, the definition covers the action and both blocking conditions, which is close to sufficient. The remaining gap is the absence of any statement about irreversibility or success behavior.

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?

There is a single required parameter at 100% schema description coverage, so the schema already defines 'path' as the folder to delete. The description adds no format, root-relative, or validation details beyond that, making the baseline of 3 appropriate.

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?

States a specific verb and resource ('Delete an empty folder') and immediately narrows the scope with two preconditions. An agent can distinguish this from delete_note or move_folder without inspecting any schema.

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 says when the tool will fail (folder non-empty, folder is vault root), which implicitly tells the agent when it is applicable. However, it never names an alternative for non-empty folders or root, nor does it state any prerequisite such as confirming the folder is empty first.

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