RetailHardHat

Create Change Request Line Item

create_change_request_line_item

Use this when working with RetailHardHat change_requests records in the connected organization. Add a financial change-request line item. 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": "create_change_request_line_item"
  }
}

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

A4/5.0

Behavior5/5

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

Beyond annotations, the description discloses a critical approval gate: no change occurs until human approval in Settings > MCP and execute_approved_action is called. It also notes administrator-configurable MCP approval requirements and that 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.

Conciseness5/5

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

The description is four tight sentences with the purpose front-loaded and approval behavior immediately following. Each sentence adds meaningful context without redundancy.

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 sufficiently covers purpose and approval behavior for a gated mutation, but leaves gaps around parameter semantics and alternative tool selection. For a nested-object create operation, field-level guidance or required-field emphasis would improve completeness.

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 the description does not explain changeRequestId or any nested data fields such as totalPrice, quantity, labor, materials, or unitPrice. The phrase 'financial line item' gives only a minimal hint about the payload.

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 states a specific verb and resource: 'Add a financial change-request line item.' The RetailHardHat change_requests context and 'line item' distinction separate it from create_change_request and update_change_request_line_item.

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 says to use the tool when working with change_requests records, which gives broad context but does not explicitly describe when to choose this over creating a change request or updating an existing line item. Usage is implied by the purpose rather than fully guided.

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?