qidi-mcp

delete_directory

Destructive

Delete a directory on the printer with a two-step confirmation that lists its contents first; use force=true to remove a non-empty directory.

Instructions

Delete a directory on the printer. Two-step confirmation, and the ticket lists what is inside first. force=true is required to delete a non-empty directory.

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

Input Schema

Name	Required	Description	Default
`path`	Yes
`force`	No
`confirm`	No
`confirm_token`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, so the description's job is to add operational detail, and it does: a two-step confirmation and a ticket that lists contents before deletion. It doesn't state whether the deletion is recoverable (trash vs. permanent) or what permissions are needed, which is a real gap 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.

Conciseness4/5

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

Three tight sentences, no filler, with the core action front-loaded. The phrase "the ticket lists what is inside first" is slightly vague on what a ticket is and when it is produced, a small clarity cost.

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?

With an output schema present, return values need no explanation, and the description covers the destructive nature, the confirmation sequence, and the force requirement. The mechanics of obtaining and passing confirm_token remain underspecified for a four-parameter destructive tool.

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 coverage is 0%, so the description must carry all parameter meaning. It fully explains force but only alludes to confirm and confirm_token through "two-step confirmation," never saying where the token comes from or what the confirm boolean does relative to it; path is left entirely implicit.

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?

Names a specific verb and resource (delete a directory) and scopes it to the printer, which separates it from delete_file and create_directory purely on the resource noun. It does not explicitly contrast itself with the closest siblings, so it stops short of a 5.

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?

"force=true is required to delete a non-empty directory" gives a concrete precondition for parameter selection, and the confirmation flow signals when a second call is needed. It never names an alternative tool or says when not to use this one, which keeps it out of 5 territory.

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

Deploy Server