RetailHardHat

Update Document Folder

update_document_folder

Destructive

Use this when working with RetailHardHat documents records in the connected organization. Rename a document folder. 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>",
      "data": "<data>"
    },
    "name": "update_document_folder"
  }
}

Input Schema

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful context beyond them: the change is not applied until a human approves the exact request and execute_approved_action is called, and org admins can configure those requirements. It does not say what happens to a rejected request or whether a partial rename can occur, but the two-step approval disclosure is substantive.

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?

Four sentences with no egregious waste, but the actual purpose ("Rename a document folder") is buried in the second sentence behind an organization-scoped boilerplate opener. Front-loading the verb would improve scanability.

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?

An output schema exists, so return values need no explanation, and the annotations plus approval disclosure cover behavior reasonably. The remaining gap is that a mutation tool with two undocumented, nested parameters provides no schema-level or prose-level guidance on the inputs it requires.

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?

Schema description coverage is 0% and neither folderId (UUID) nor data.name (1-200 chars) is mentioned in the description. "Rename" only loosely implies that a name value is supplied; an agent gets no help from the prose about which folder identifier to pass or the name length constraint.

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?

"Rename a document folder" states a specific verb and resource, which cleanly separates it from create_document_folder, delete_document_folder, and get_document_folder. The leading boilerplate phrase "working with RetailHardHat documents records" is vague padding, but the concrete sentence that follows carries the meaning.

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 description explains the approval workflow precondition (human approval in Settings > MCP, then execute_approved_action), which is genuine usage context. However, it never states when to pick this over siblings such as apply_document_folder_to_all_sites or set_document_folder_visibility, nor what conditions make a rename inappropriate.

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?