nc-mcp-server

delete_trash_item

DestructiveIdempotent

Permanently delete a single file or folder from the trash bin. Irreversible action that cannot be undone.

Instructions

Permanently delete a single item from the trash bin.

This action is irreversible. The file or folder will be permanently destroyed and cannot be recovered.

Args: trash_path: The trash path identifier from list_trash (e.g. "document.txt.d1711000000").

Returns: Confirmation message.

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": {
      "trash_path": "<trash_path>"
    },
    "name": "delete_trash_item"
  }
}

Input Schema

Name	Required	Description	Default
`trash_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the practical consequence that the item is permanently destroyed and cannot be recovered, and clarifies that only a single item is affected. This enriches the safety profile without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and irreversibility warning are front-loaded, and the Args/Returns structure is easy to scan. There is minor redundancy between 'permanently delete,' 'irreversible,' and 'cannot be recovered,' but it does not detract from clarity.

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?

For a one-parameter destructive operation, the description covers the parameter's source, the effect of the action, and the expected return. Combined with the annotations and the presence of an output schema, nothing essential is missing for an agent to invoke it correctly.

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?

The schema only defines trash_path as a string with no description, while the tool description explains that it is the identifier returned by list_trash and provides a concrete example format. This fully compensates for the 0% schema description coverage.

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 states a specific verb ('delete'), a specific resource ('single item from the trash bin'), and the permanence of the action. It is clearly distinguished from siblings like empty_trash and restore_trash_item by the 'single item' and 'from the trash bin' scope.

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 does not explicitly name alternatives or state when to use restore_trash_item vs. empty_trash. It implies selection through 'from the trash bin' and 'irreversible,' but leaves the routing decision to the agent.

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

Deploy Server