Skip to main content
Glama

woo_helper_put_invoices

Change only specified cvrt-woo-helper invoice settings, keep stored API keys when blank, and use dry-run preview before enabling live invoices for paid orders.

Instructions

Change cvrt-woo-helper invoice settings; only the keys given change, an invalid value is a 400 and nothing is written. api_keys is WRITE-ONLY (a blank key keeps the stored one) and is never returned; clear_api_keys deletes keys. dry_run stays on until explicitly switched off: with it off, paid orders create REAL invoices in the live ledger.

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>"
    },
    "name": "woo_helper_put_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
titleNo
remarkNo
dry_runNotrue = build and show the request only, never write to the provider
enabledNoCreate invoices for paid orders
refundsNoCredit notes / cancellation for refunds
api_keysNoWRITE-ONLY API keys per provider; blank keeps the stored key
einvoiceNoE-invoice (XRechnung/ZUGFeRD) where the provider supports it
providerNo
own_emailNoSeparate 'Your invoice' email
referenceNoInvoice reference; must contain {order_number} or {order_id}
price_modeNo
vat_id_metaNoOrder meta key holding the customer's VAT id
introductionNo
attach_emailsNoEmails that get the invoice PDF
sevdesk_unityNo
clear_api_keysNoDelete these providers' stored keys
create_contactsNoCreate provider contacts for customers
sevdesk_templateNo
trigger_statusesNoAlso create when a paid order reaches these statuses
lexware_unit_nameNo
sevdesk_letterpaperNo
lexware_print_layoutNo
sevdesk_contact_personNo
sevdesk_payment_methodNo
lexware_payment_conditionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior5/5

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

With no annotations, the description carries the full load and does so: it discloses atomicity ('an invalid value is a 400 and nothing is written'), write-only semantics for api_keys with blank-means-keep, the destructive effect of clear_api_keys, and the default-safe dry_run posture with explicit warning that live mode creates REAL invoices. These are exactly the behavioral traits that affect the safety of a call and are not visible in the schema.

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?

Front-loaded with the purpose and extremely dense — nearly every clause conveys a distinct constraint. It is only four sentences for a 26-parameter tool, so the concision is a virtue; the semicolon-heavy packing slightly hurts scannability but nothing is wasted.

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?

For a 26-parameter mutation tool with no annotations and no output schema, the description covers the risky behaviors well but leaves the agent without any expectation of the response (success payload, validation error shape beyond the 400 note) or guidance on the many provider-specific fields it never mentions. Adequate but not complete.

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 coverage is 50% across 26 parameters, so the schema does part of the work. The description adds real meaning for the highest-risk fields (dry_run, api_keys, clear_api_keys, enabled, refunds), but it says nothing about provider, price_mode, einvoice, reference, own_email, trigger_statuses, or the sevdesk_*/lexware_* fields that reference #/properties/sevdesk_contact_person — a non-obvious shared type that would benefit from explanation.

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?

States a specific verb and resource: 'Change cvrt-woo-helper invoice settings'. It is clearly a settings-mutation tool, and the phrasing 'only the keys given change' distinguishes it as a partial/PUT-style update rather than a full replace. It does not name a sibling (e.g. woo_helper_get_invoices for reading), so it falls short of the sibling-differentiation bar for a 5.

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?

The description implies partial-update usage ('only the keys given change') and provides the crucial gate on dry_run being off to create real invoices. It never says when to prefer this over woo_helper_update_settings or how to read current values first (woo_helper_get_invoices). Usage is implied rather than stated.

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