RetailHardHat

Delete Invoice

delete_invoice

Destructive

Use this when working with RetailHardHat invoices records in the connected organization. Delete an invoice record and its normal associations. 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": {
      "bidId": "<bidId>",
      "invoiceId": "<invoiceId>"
    },
    "name": "delete_invoice"
  }
}

Input Schema

Name	Required	Description	Default
`bidId`	Yes
`invoiceId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description goes far beyond the standard 'destructive' annotation by explaining the complex approval workflow. It details the exact mechanism of delayed mutation—requiring MCP approval and subsequent execution—which is vital behavioral context for an AI agent.

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 well-structured, prioritizing the scope and safety mechanism upfront. While slightly wordy, the complexity of the approval workflow necessitates the detail provided, making the structure logical.

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?

The definition is fundamentally incomplete regarding its inputs. Because the required parameters (bidId, invoiceId) are not described, an AI agent cannot confidently select or correctly structure the input data needed for this tool call.

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?

The description provides zero semantic meaning for the required parameters, bidId and invoiceId. Given that schema coverage is 0%, the description fails to compensate, leaving the agent to guess the necessary format or constraints of these UUID fields.

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 purpose is perfectly clear: it deletes an invoice record. It specifically scopes the action to 'RetailHardHat invoices records' and notes that it deletes 'normal associations,' clearly distinguishing its function.

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 essential usage rules by explaining that the operation is not immediate. It dictates that the action only occurs after a human approves the request via Settings > MCP and calls execute_approved_action, establishing the proper execution 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?