RetailHardHat

Execute Approved Action

execute_approved_action

Destructive

Execute a human-approved action once. Arguments are loaded from the immutable approval, never supplied again. Failed or executing actions cannot be retried automatically.

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": {
      "approvalId": "<approvalId>"
    },
    "name": "execute_approved_action"
  }
}

Input Schema

Name	Required	Description	Default
`approvalId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds behavioral value by noting that arguments are loaded from the immutable approval rather than being supplied manually. This, combined with the annotations indicating it is a destructive action (destructiveHint: true), gives a complete picture of the tool's execution profile.

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

Conciseness5/5

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

The definition is highly concise and professional. Both sentences are critical to understanding the tool's behavior—one describing the mechanism (loading arguments) and the other describing the operational limits (no retries).

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?

Given that it is a critical, destructive operation with fixed behaviors (once, no retries), the description is exceptionally complete. It covers the state transition (execution) and the failure conditions (immutability/no retries).

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

Parameters3/5

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

Schema coverage is 0%, so the description does not add complex semantic meaning to the required 'approvalId.' Since the parameter is a simple ID, the baseline score of 3 applies, acknowledging the schema is the primary source of truth.

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 executes a 'human-approved action.' While the context of the surrounding tools suggests this, the description clearly defines its role as the final execution step rather than the initiation of a request.

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

Usage Guidelines5/5

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

The tool provides explicit usage guidelines by stating that actions run 'once,' arguments are 'immutable,' and that 'Failed or executing actions cannot be retried automatically.' This defines critical operational boundaries for the agent.

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?