RetailHardHat

Update Approval Flow

update_approval_flow

Destructive

Configure/edit approval_flow; server-owned fields are excluded. 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": {
      "id": "<id>",
      "data": "<data>"
    },
    "name": "update_approval_flow"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`data`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3.1/5.0

Behavior4/5

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

While the annotations already mark this as a destructive write operation (destructiveHint: true), the description provides a valuable operational detail: 'server-owned fields are excluded.' This helps the agent construct a valid payload by knowing which fields it should not attempt to modify.

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 description is brief and generally efficient. The two sentences communicate the scope and a key constraint without excessive filler, achieving a functional level of conciseness.

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

Completeness2/5

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

Given the high complexity of the nested schema (including UUID arrays and step objects), the description is woefully incomplete. It provides zero semantic help for the numerous complex inputs required for a successful call.

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 coverage is 0%, meaning the description must describe the parameters. It only provides high-level context on the flow but fails to define the meaning, purpose, or constraints of the critical parameters like 'steps' or 'entityType'.

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 clearly states the tool's purpose as 'Configure/edit approval_flow.' This verb choice differentiates it from sibling tools like 'create_approval_flow' or 'get_approval_flow,' defining its scope as an update operation.

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?

It provides context by stating that 'business workflow approvals always apply,' which gives a usage constraint. However, it lacks explicit guidance on when this tool is preferable over other mutation siblings.

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?