Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

invoices_export_saga_xml

Read-onlyIdempotent

Export invoices as Saga XML for accounting software integration, applying filters like date range and status. Get XML text ready for Saga C import.

Instructions

Export invoices in Saga XML format for accounting software integration (e.g., Saga C). Accepts the same filters as invoices_export_csv. Returns XML text content.

Input Schema

NameRequiredDescriptionDefault
sortNoSort field
orderNoSort order
dateToNoEnd date (YYYY-MM-DD, issue date)
searchNoSearch term for invoice number or client name
statusNoFilter by invoice status
clientIdNoFilter by client UUID
dateFromNoStart date (YYYY-MM-DD, issue date)
companyIdNoCompany UUID override (uses active company if not set)
directionNoFilter by direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.57
    • addedInput schema / properties / dateFrom
      Added value: +{
+  "description": "Start date (YYYY-MM-DD, issue date)",
+  "type": "string"
+}
    • addedInput schema / properties / dateTo
      Added value: +{
+  "description": "End date (YYYY-MM-DD, issue date)",
+  "type": "string"
+}
    • removedInput schema / properties / from
      Removed value: -{
-  "description": "Start date (YYYY-MM-DD)",
-  "type": "string"
-}
    • removedInput schema / properties / to
      Removed value: -{
-  "description": "End date (YYYY-MM-DD)",
-  "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 declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds that the payload is returned as XML text content, which matters because there is no output schema. It omits any note on size limits or whether large exports route through exports_download.

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 short sentences, front-loaded with the format and purpose, no filler. Slightly terse on the return side but every sentence earns its place.

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 read-only export tool with full schema coverage, the description covers purpose, filters and return type. The main remaining gap is handling of large result sets (exports_download exists as a sibling), which an agent might want to know.

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% with 9 documented params and 4 enums, so the schema carries parameter meaning. The description only adds that filtering mirrors invoices_export_csv, which is a useful cross-reference but not additional semantics per parameter.

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 (export), resource (invoices), and output format (Saga XML), which separates it from invoices_export_csv and invoices_export_zip. It does not explicitly distinguish itself from invoices_xml or invoices_export_receipts_saga_xml, but the resource+format pair is specific enough to route correctly.

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

Usage Guidelines4/5

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

Gives the use context (accounting software integration, e.g. Saga C) and cross-references invoices_export_csv as the equivalent-filter alternative, implying CSV is the other choice. No explicit when-not condition, but the context is clear.

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