RetailHardHat

Move Site Document

move_site_document

Destructive

Move a site document into a folder, or null for the root. Confidential access and same-site relationships are enforced. 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>",
      "data": "<data>"
    },
    "name": "move_site_document"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes
`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

A4.6/5.0

Behavior5/5

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

The description provides crucial context regarding operational policies (e.g., 'Confidential access and same-site relationships are enforced') and external workflow requirements ('MCP approval requirements... business workflow approvals always apply'), adding depth far beyond the 'destructiveHint' annotation.

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 tool is efficiently structured across three sentences. Each sentence is front-loaded with a specific piece of critical information (Function, Security, Process workflow), with no redundant phrasing.

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?

The definition is highly complete. It successfully describes what the tool does, the security guardrails it operates under, and the necessary business processes that accompany the mutation, making it robust for an agent to understand.

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

Parameters4/5

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

Given that schema coverage is 0%, the description is essential. It clarifies the semantic meaning of the 'null' input for the folder ID, indicating it refers to the document being moved to the root folder rather than an absent folder.

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 clearly identifies the action ('Move'), the resource ('site document'), and the target/scope ('into a folder, or null for the root'). It leaves no ambiguity about the specific operation performed.

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 sets strong prerequisites by enforcing 'confidential access and same-site relationships,' which guides the agent on the operational scope. While it doesn't explicitly name sibling alternatives, it clearly defines the boundary of its functionality.

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?