Skip to main content
Glama

woo_helper_create_invoice

Creates a real, irreversible invoice in the live sevDesk/Lexware ledger for a WooCommerce order; requires confirm:true and a prior preview.

Instructions

DESTRUCTIVE, IRREVERSIBLE: creates a REAL invoice for this order in the live sevDesk/Lexware ledger. An invoice there cannot be deleted, only cancelled with a cancellation invoice. Refused with 409 while dry-run is on. Check woo_helper_get_invoice_order (preview) first. Requires confirm:true.

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": {
      "site": "<site>",
      "order_id": "<order_id>",
      "confirm": "<confirm>"
    },
    "name": "woo_helper_create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
confirmYesMust be true: creates a real, undeletable invoice
order_idYesWooCommerce order id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it labels the operation destructive and irreversible, explains the concrete consequence (cannot be deleted, only offset by a cancellation invoice), and discloses the dry-run 409 refusal behavior. This is exactly the operational context an agent needs before a write.

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?

Three short sentences, front-loaded with the destructive warning, then the irreversible consequence, then prerequisites. Every sentence adds distinct decision-relevant information with no filler.

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 a 3-parameter mutation with no output schema, the definition covers safety, irreversibility, failure mode, prerequisite preview, and confirmation requirement. Nothing an agent needs in order to invoke it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so site, order_id, and confirm are already documented, and the description's 'Requires confirm:true' largely restates the schema's const/enum constraint. Baseline 3 applies since the schema does the heavy lifting and the description adds no new per-parameter syntax.

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?

States a specific verb and resource ('creates a REAL invoice for this order in the live sevDesk/Lexware ledger') and immediately distinguishes it from the preview sibling woo_helper_get_invoice_order. An agent can tell exactly what this tool does and which counterpart it is not.

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?

Gives an explicit ordering rule ('Check woo_helper_get_invoice_order (preview) first') and an environmental precondition ('Refused with 409 while dry-run is on'), plus the confirm gate. When-to-use and when-it-will-fail are both stated rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools