RetailHardHat

Update Change Request

update_change_request

Destructive

Use this when working with RetailHardHat change_requests records in the connected organization. Edit the request without bypassing its business approval workflow. 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": {
      "changeRequestId": "<changeRequestId>",
      "data": "<data>"
    },
    "name": "update_change_request"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes
`changeRequestId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.5/5.0

Behavior5/5

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

The description adds critical behavior beyond the destructive/read-only annotations: changes do not occur until a human approves the exact request and execute_approved_action is called. It also clarifies that MCP approval requirements are administrator-configurable while business workflow approvals always apply.

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 description is front-loaded and compact, with the approval workflow stated clearly. The opening sentence is somewhat generic, but the remaining sentences carry necessary behavioral context.

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?

It covers the approval workflow and mutation safety well, and an output schema exists so return values need not be explained. However, for a nested data object with many fields and 0% schema description coverage, the description omits what fields can be updated and how the data object should be structured.

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?

Schema description coverage is 0%, and the description provides no field-level meaning for changeRequestId or the nested data object's many editable properties. It does not compensate for the undocumented parameters.

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 gives a specific verb and resource: 'Edit the request' for RetailHardHat change_requests records. It is distinguishable from create/get/delete/update_change_request_line_item siblings, though it does not explicitly name alternatives.

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 establishes when the tool applies ('working with RetailHardHat change_requests records') and highlights the approval prerequisite, but it does not explicitly compare usage against siblings such as get_change_request, create_change_request, or update_change_request_line_item.

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?