RetailHardHat

Delete Site Document

delete_site_document

Destructive

Use this when working with RetailHardHat documents records in the connected organization. Remove a site document using the application's normal file-deletion rules. 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": {
      "siteId": "<siteId>",
      "documentId": "<documentId>"
    },
    "name": "delete_site_document"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes
`documentId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The annotations already mark this as destructive and non-read-only, and the description adds important workflow context: deletion follows normal file-deletion rules and no change occurs until human approval in Settings > MCP followed by execute_approved_action. It also notes configurable MCP approval requirements and mandatory business workflow approvals.

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 approval details are valuable and front-loaded enough to guide safe use. The opening sentence is somewhat awkward and low-value, but the rest of the description is appropriately compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the destructive action's approval workflow well, and an output schema exists so return values need not be explained. However, for a destructive tool with two required parameters and 0% schema description coverage, the description leaves parameter meaning undocumented.

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

Parameters1/5

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

The schema has 0% description coverage for two required UUID parameters, siteId and documentId. The description never explains either parameter, so it does not compensate for the schema gap.

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: "Remove a site document" and refers to "file-deletion rules." This distinguishes it from read/update/attach siblings and from project/task document deletion variants by naming the site-document scope, though the opening sentence is awkward filler.

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 phrase "Use this when working with RetailHardHat documents records" is broad and does not give a concrete when-to-use condition or mention alternatives such as delete_project_document or move_site_document. It does clarify the required approval follow-up with execute_approved_action, which is useful workflow guidance.

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?