Storno CLI

Official

Overview Schema Source Related Servers Discussions Admin

recurring_invoices_create

Create a recurring invoice template that auto-generates invoices on a defined frequency and schedule, with flexible pricing rules per line item.

Instructions

Create a new recurring invoice template. The system will automatically generate invoices based on the specified frequency and schedule. Supports fixed, updated_product, bnr_rate and bnr_rate_markup pricing rules on line items.

Input Schema

Name	Required	Description
`lines`	Yes	Array of line items (minimum 1 required)
`notes`	No	Notes printed on every generated document. Placeholders: [[luna]], [[luna±N]], [[an]], [[an±N]], [[luna_nr]], [[curs]] (the BNR rate note), [[suma:EXPR]] (an amount computed from EXPR, e.g. [[suma:1900*curs]] = 1,900 EUR at the BNR rate of the issue date; names: curs, curs_EUR, curs_USD…, sold, sold_anterior, rata), and with a running balance: [[sold]] (left after this invoice), [[sold_anterior]] (before), [[rata]] (deducted now). Amounts print in Romanian format (9.633,00).
`balance`	No	Running balance in RON (e.g. an investment recovered through rent reductions). Reduced on every issuance by balanceStep; printed with [[sold]]. The template pauses when it reaches zero.
`clientId`	Yes	UUID of the client
`currency`	Yes	ISO 4217 currency code (e.g., RON, EUR)
`seriesId`	Yes	UUID of the document series
`stopDate`	No	ISO 8601 date to stop generation (YYYY-MM-DD)
`companyId`	No	Company UUID (overrides configured default)
`frequency`	Yes	How often to generate invoices
`reference`	No	Human-readable reference for this recurring invoice
`balanceStep`	No	Expression deducted from balance per issuance, e.g. "1900*curs" (1,900 EUR at the BNR rate of the issue date). Names: curs, curs_EUR…, sold_anterior. The last deduction is capped at what is left.
`dueDateDays`	No	Days after issue date for due date (required if dueDateType is days)
`dueDateType`	Yes	How due date is calculated. days = N days after issue. fixed_day = fixed day of month.
`documentType`	Yes	Document type to generate
`frequencyDay`	Yes	Day of month for generation (1-31)
`paymentTerms`	No	Payment terms text
`autoEmailTime`	No	Time to send email (HH:mm, default: "09:00")
`frequencyMonth`	No	Month for yearly generation (1-12, required if frequency is yearly)
`penaltyEnabled`	No	Enable late payment penalties (default: false)
`dueDateFixedDay`	No	Fixed day of month for due date (1-31, required if dueDateType is fixed_day)
`invoiceTypeCode`	Yes	Tax regime / invoice type code
`autoEmailEnabled`	No	Auto-send email on invoice generation (default: false)
`nextIssuanceDate`	Yes	ISO 8601 date for the first invoice generation (YYYY-MM-DD)
`penaltyGraceDays`	No	Grace period in days before penalties apply
`autoEmailDayOffset`	No	Days offset for email sending (default: 0)
`penaltyPercentPerDay`	No	Daily penalty percentage

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.0.51Oct 14, 2026

addedInput schema / properties / balance

Added value: +{
+  "anyOf": [
+    {
+      "type": [
+        "number",
+        "string"
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Running balance in RON (e.g. an investment recovered through rent reductions). Reduced on every issuance by balanceStep; printed with [[sold]]. The template pauses when it reaches zero."
+}

addedInput schema / properties / balanceStep

Added value: +{
+  "description": "Expression deducted from balance per issuance, e.g. \"1900*curs\" (1,900 EUR at the BNR rate of the issue date). Names: curs, curs_EUR…, sold_anterior. The last deduction is capped at what is left.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / lines / items / properties / priceExpression

Added value: +{
+  "description": "With priceRule=expression: the unit price in the document currency computed at issuance, e.g. \"2000*curs - rata\" (2,000 EUR at the BNR rate minus what this issuance deducts from the running balance). Names: curs, curs_EUR…, rata, sold, sold_anterior, luna_nr, an. Negative results become 0.",
+  "type": "string"
+}

changedInput schema / properties / lines / items / properties / priceRule / description

Previous value: -"Pricing rule. fixed: unitPrice as-is. updated_product: refresh from linked product on each issuance. bnr_rate: convert from referenceCurrency at BNR rate. bnr_rate_markup: same as bnr_rate plus markupPercent."New value: +"Pricing rule. fixed: unitPrice as-is. updated_product: refresh from linked product on each issuance. bnr_rate: convert from referenceCurrency at BNR rate. bnr_rate_markup: same as bnr_rate plus markupPercent. expression: unitPrice computed at issuance from priceExpression (document currency), e.g. \"2000*curs - rata\"."

changedInput schema / properties / lines / items / properties / priceRule / enum

Previous value: -[
-  "fixed",
-  "updated_product",
-  "bnr_rate",
-  "bnr_rate_markup"
-]New value: +[
+  "fixed",
+  "updated_product",
+  "bnr_rate",
+  "bnr_rate_markup",
+  "expression"
+]

changedInput schema / properties / notes / description

Previous value: -"Internal notes"New value: +"Notes printed on every generated document. Placeholders: [[luna]], [[luna±N]], [[an]], [[an±N]], [[luna_nr]], [[curs]] (the BNR rate note), [[suma:EXPR]] (an amount computed from EXPR, e.g. [[suma:1900*curs]] = 1,900 EUR at the BNR rate of the issue date; names: curs, curs_EUR, curs_USD…, sold, sold_anterior, rata), and with a running balance: [[sold]] (left after this invoice), [[sold_anterior]] (before), [[rata]] (deducted now). Amounts print in Romanian format (9.633,00)."

First observedv1.0.17Aug 4, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent mutation. The description adds useful context that invoices will be generated automatically according to frequency and schedule, but it omits operational details like pause behavior, required permissions, or what the response returns.

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 core action and generation behavior. There is little wasted text, and the key concept appears immediately.

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 complex creation tool with 26 parameters, 10 required fields, and no output schema, the description is quite thin. It covers the core behavior and pricing-rule support, but leaves scheduling, auto-email, balance, and return-value context to the schema or unstated.

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 schema already documents all 26 parameters in detail. The description mentions pricing rules but only lists four of the five schema enum values, omitting expression, and adds no syntax or format guidance beyond the schema.

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?

The description states a specific verb and resource: creating a recurring invoice template, with automatic invoice generation. It distinguishes this from one-off invoice creation by emphasizing recurrence and scheduling, though it does not explicitly name sibling alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains what the tool does but gives no explicit guidance on when to use it versus alternatives such as recurring_invoices_update, recurring_invoices_issue_now, or invoices_create. The agent must infer that this is for initial template creation.

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

Deploy Server

recurring_invoices_create

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools