Skip to main content
Glama
stornoro

Storno CLI

by stornoro

invoices_update

Update an existing draft invoice by modifying details or replacing its line items. Only draft invoices can be updated; issued invoices must be canceled instead.

Instructions

Update an existing draft invoice. Only invoices with status "draft" can be updated. When updating the lines array, the entire array is replaced — include all lines you want to keep. Once issued, use invoices_cancel instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesInvoice UUID to update
linesNoInvoice line items. WARNING: replaces all existing lines — include every line you want to keep.
notesNoPublic notes visible to the client
dueDateNoPayment due date (YYYY-MM-DD)
clientIdNoClient UUID
currencyNoISO 4217 currency code
issuerIdNoIssuer ID number
languageNoDocument language for PDF generation (default: ro)
mentionsNoAdditional legal mentions
seriesIdNoInvoice series UUID
companyIdNoCompany UUID override (uses active company if not set)
issueDateNoInvoice issue date (YYYY-MM-DD)
deputyAutoNoDeputy vehicle registration
deputyNameNoDeputy/representative name
issuerNameNoName of person issuing the invoice
salesAgentNoSales agent name
orderNumberNoPurchase order number
plataOnlineNoEnable online payment via Stripe
platitorTvaNoWhether sender is VAT payer
receiverCifNoReceiver tax ID / CIF
vatIncludedNoWhen used with autoApplyVatRules, sets whether unit prices include VAT on all lines. Ensures correct totals after VAT rules change rates.
documentTypeNoDocument type
exchangeRateNoExchange rate relative to RON
internalNoteNoInternal note (not visible to client)
paymentTermsNoPayment terms description
receiverNameNoReceiver name (when no client entity exists)
taxPointDateNoTax point date (YYYY-MM-DD)
paymentMethodNoPayment method: bank_transfer, cash, card, cheque, other
tvaLaIncasareNoVAT on collection / TVA la încasare
ublExtensionsNoUBL extension fields for advanced e-Factura compliance. These map directly to UBL XML elements not covered by the standard invoice fields.
buyerReferenceNoBuyer reference identifier
contractNumberNoContract reference number
penaltyEnabledNoEnable late payment penalty
invoiceTypeCodeNoTax regime / invoice type code
deliveryLocationNoDelivery address
parentDocumentIdNoParent document UUID (for credit notes)
penaltyGraceDaysNoGrace period before penalty applies
projectReferenceNoProject reference number
taxPointDateCodeNoTax point date code
autoApplyVatRulesNoAuto-apply VAT rules (reverse charge for VIES-valid EU clients, OSS destination rate for non-VIES EU clients). Default: false.
showClientBalanceNoShow client balance on invoice
deputyIdentityCardNoDeputy ID card number
businessProcessTypeNoBusiness process type
penaltyPercentPerDayNoDaily penalty percentage
tenderOrLotReferenceNoTender or lot reference
despatchAdviceReferenceNoDespatch advice reference
buyerAccountingReferenceNoBuyer accounting reference
invoicedObjectIdentifierNoInvoiced object identifier
receivingAdviceReferenceNoReceiving advice reference
Behavior3/5

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

No annotations are provided, so the description carries the load for behavior disclosure. It does well to warn about the destructive lines-array replacement behavior, which is a subtle and potentially data-lossy trait. However, it does not disclose the return value, whether partial updates are allowed (beyond lines), or any permission/auth requirements. The key destructive behavior is the most important disclosure and is present, so a 3 is fair.

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?

Three sentences with no waste. The critical facts (draft-only, lines replacement, cancel alternative) are front-loaded and each sentence earns its place. Could arguably be slightly more structured, but it is appropriately compact.

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?

For a complex 49-parameter tool with nested UBL extensions, the description covers the two most operationally critical behaviors: the draft-only restriction and the destructive lines replacement. Since there's no output schema, a brief note on the update response would be useful, but the schema richly documents all parameters. The description is sufficient for correct invocation despite the tool's complexity.

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 the baseline starts at 3. The description adds value for the lines parameter with its replacement warning, which is genuinely helpful. However, it doesn't add meaning beyond the schema for the other 48 parameters. Coverage is high so the schema does the heavy lifting; the lines warning justifies maintaining the baseline.

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 description clearly states the verb (update), the specific resource (existing draft invoice), and includes a critical scope constraint (only draft status). It also distinguishes from the sibling tool invoices_cancel by explicitly naming it as the alternative for issued invoices, which differentiates it well from the many invoice-related siblings.

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?

The description provides explicit usage conditions: only draft-status invoices can be updated, and once issued, invoices_cancel should be used instead. This gives clear when-to-use and when-not-to-use guidance, plus explicitly names the fallback tool for the excluded case.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stornoro/storno-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server