Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

invoices_export_receipts_saga_xml

Read-onlyIdempotent

Exports outgoing invoice payment receipts in SAGA XML format for accounting software integration; filter by payment date or override cash, bank, and card accounts.

Instructions

Export payment receipts (incasari) in Saga XML format. Exports the outgoing invoice payments in the given period (all of them when no period is passed) for accounting software integration. Use accountCash/accountBank/accountCard to override the chart-of-accounts for this export (defaults come from the company’s stored SAGA settings; SAGA requires the leaf analytic for cards, e.g. 5125.2).

Input Schema

NameRequiredDescriptionDefault
dateToNoEnd date (YYYY-MM-DD, payment date)
dateFromNoStart date (YYYY-MM-DD, payment date). Pass a period: without one the whole history is exported.
companyIdNoCompany UUID override (uses active company if not set)
accountBankNoOverride bank transfer account (e.g. 5121)
accountCardNoOverride card analytic account (e.g. 5125.2)
accountCashNoOverride cash account (e.g. 5311)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.57
    • addedInput schema / properties / dateFrom
      Added value: +{
+  "description": "Start date (YYYY-MM-DD, payment date). Pass a period: without one the whole history is exported.",
+  "type": "string"
+}
    • addedInput schema / properties / dateTo
      Added value: +{
+  "description": "End date (YYYY-MM-DD, payment date)",
+  "type": "string"
+}
  2. First observedv1.0.17

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is added context — and it delivers: no period means the whole history is exported, account defaults come from the company's stored SAGA settings, and card accounts require a leaf analytic (e.g. 5125.2). It stops short of saying what the call actually returns (inline XML vs. a downloadable artifact).

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 tight sentences, front-loaded with purpose and scope, then the account-override caveat. The parentheticals (incasari, the 5125.2 example) are load-bearing rather than filler.

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 6-parameter read-only export with no output schema, the description covers scope, period semantics, and account overrides thoroughly. The one meaningful gap is the return shape — whether the XML is returned inline, as a base64 blob, or as a file reference — which the agent cannot infer without an output schema.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description still adds value by explaining the default source for the three account parameters (company SAGA settings) and the leaf-analytic constraint for cards, neither of which is in the schema. The dateFrom default behavior is restated from the schema but tied explicitly to export scope.

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?

Names a specific verb and resource (

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 usage for accounting-software integration and states the period default, which is helpful context. However, it never names an alternative or an exclusion — notably it does not distinguish this from the near-identically named sibling invoices_export_payments_saga_xml, so the agent must infer which one to call.

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