RetailHardHat

Delete Purchase Item

delete_purchase_item

Destructive

Use this when working with RetailHardHat purchase_lists records in the connected organization. Delete a purchase 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": {
      "siteId": "<siteId>",
      "purchaseItemId": "<purchaseItemId>"
    },
    "name": "delete_purchase_item"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes
`purchaseItemId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.9/5.0

Behavior5/5

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

The description dramatically enhances behavioral transparency beyond the `destructiveHint: true` annotation. It clarifies that the action is not immediate, requiring an intermediary approval process and an external call to `execute_approved_action`.

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 explanation of the approval workflow necessitates multiple sentences, making it less concise than other definitions. However, the information provided is vital and cannot be condensed without losing critical context.

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

Completeness4/5

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

The description is very complete regarding the operational context and constraints of the deletion. By outlining the MCP approval requirements, it gives the agent all necessary context to use the tool correctly within the organization's workflow.

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%, and the description offers absolutely no semantic meaning for the 'siteId' or 'purchaseItemId' beyond their role in the 'purchase_lists' record. The description fails to compensate for the missing schema details.

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 identifies the resource ('purchase_lists records') and the action ('delete a purchase item'). While it doesn't explicitly mention the UUID parameters, the scope is well-defined relative to the retail hard hat context.

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?

It provides extremely clear usage instructions by mandating a specific workflow: 'No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called.' This defines the exact operational context.

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?