RetailHardHat

Delete Document Folder

delete_document_folder

Destructive

Use this when working with RetailHardHat documents records in the connected organization. Delete a folder using existing nonempty-folder safeguards. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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": {
      "folderId": "<folderId>"
    },
    "name": "delete_document_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folderId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3.4/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses crucial behavior: deletion is gated by human approval in Settings > MCP, requires execute_approved_action, and is subject to configurable organization approval requirements. It also notes nonempty-folder safeguards, which is exactly the kind of operational context an agent needs before calling a destructive tool.

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

Conciseness3/5

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

The useful approval details are present, but the first sentence is boilerplate that delays the actual purpose, which appears in the second sentence. The remaining sentences earn their place, but the opening could be removed or replaced with the action.

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 destructive tool with an output schema and destructive annotation already present, the description covers the important approval workflow and nonempty-folder safeguards. It remains incomplete about the folderId parameter and the exact behavior when the folder is nonempty.

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

Parameters2/5

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

The schema has 0% description coverage and the description does not explain folderId at all, not even that it must identify an existing folder. The UUID format is only in the schema. With a low-coverage single parameter, the description fails to compensate.

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?

The description states a specific verb and resource: "Delete a folder" within RetailHardHat documents records. It does not distinguish this from sibling document-deletion tools such as delete_project_document or delete_site_document, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

The opening sentence "Use this when working with RetailHardHat documents records" is generic context, not a real usage condition. It gives no guidance on when to choose this over delete_project_document, delete_site_document, or update_document_folder, and gives no explicit exclusions.

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

All RetailHardHat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?