RetailHardHat

Create Invoice

create_invoice

Use this when working with RetailHardHat invoices records in the connected organization. Create a bid invoice. Does not execute payment or mark it paid. 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>",
      "data": "<data>"
    },
    "name": "create_invoice"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes
`bidId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description goes beyond simple annotation by detailing the operational behavior of the tool. It informs the agent that no change occurs until a human approves the request via 'Settings > MCP' and that the dedicated action `execute_approved_action` must be called.

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 definition is not overly wordy, but it takes time to process the operational workflow. However, it is well-structured, moving logically from general context to specific limitations and eventual execution requirements.

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?

For an agent, this description is highly complete. It defines not only *what* to create but also *when* the creation is finalized (after MCP approval) and *how* that final execution is triggered, providing all necessary operational context.

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?

Despite the high importance of the tool, parameter semantics are extremely weak. Given that schema description coverage is 0%, the description fails entirely to add meaning to the required inputs like `bidId` or the fields within the `data` object.

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 tool's purpose is perfectly clear: to 'Create a bid invoice.' It specifies the context of use ('RetailHardHat invoices records') and correctly identifies the type of invoice, distinguishing it from general document creation.

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?

This definition provides critical usage constraints by stating that it 'Does not execute payment or mark it paid.' It sets clear expectations regarding the non-immediate nature of the action and the required follow-up approval workflow.

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?