mcp-mac-control

by dockndevai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Delete a path (to Trash)

delete_path

Destructive

Move files or folders to Trash for recoverable deletion, respecting path allowlists and protected locations.

Instructions

Move a file or folder to the Trash (recoverable). Requires admin mode AND MACCTL_ALLOW_DELETE=true. Honours the path allowlist and refuses protected paths.

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_path"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Path to trash (supports ~).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description adds critical behavioral details: the operation is recoverable (Trash), requires specific permissions, honors an allowlist, and refuses protected paths. This significantly enriches the agent's understanding of safety and side effects.

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 sentences convey all essential information with no fluff. The primary action is front-loaded, and constraints are succinctly listed in the second sentence.

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 single-parameter mutation tool with no output schema, the description fully covers how to invoke it correctly: prerequisites, safety restrictions, and the recoverable nature of the operation. Nothing an agent needs to call it successfully is missing.

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?

The input schema already documents the only parameter ('path' with 'supports ~') at 100% coverage. The description adds that the path can be a file or folder, which is a minor clarification but does not carry substantial extra semantic weight.

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 uses a specific verb ('Move') and resource ('file or folder') and clarifies the target ('to the Trash (recoverable)'). This clearly differentiates it from permanent deletion and makes the tool's function unmistakable.

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

Usage Guidelines4/5

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

The description provides clear usage context by stating the required admin mode, MACCTL_ALLOW_DELETE flag, and path allowlist constraints. It does not explicitly name alternatives, but there are no sibling delete tools, so these conditions effectively guide when the tool can be invoked.

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