Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

invoices_export_csv

Read-onlyIdempotent

Export a filtered invoice list to CSV with UTF-8 BOM for Excel compatibility; supports status, direction, date range, client, and search filters. Max 10,000 invoices.

Instructions

Export a filtered list of invoices to CSV format. Accepts the same filters as invoices_list (status, direction, date range, client, etc.). Returns CSV text with UTF-8 BOM for Excel compatibility. Max 10,000 invoices; use invoices_export_zip for large exports with files.

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

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description's added value is the 10,000-invoice hard cap and the UTF-8 BOM encoding detail — both operationally relevant. It does not discuss permissions or how large results are streamed/truncated at the cap, keeping it short of a 5.

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, zero filler, with the capability stated first and the size-cap alternative last. Every sentence contributes a distinct fact (what it does, filter parity, output encoding, limit).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description covers the return value (CSV text with BOM), the size ceiling, and the escalation path to the zip sibling. Nothing an agent needs to call this correctly is missing.

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 enum values for status, direction, sort and order, so the schema already carries parameter meaning. The description's "status, direction, date range, client, etc." merely mirrors that and adds no format or default details beyond the schema.

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?

States a specific verb and resource ("Export ... invoices to CSV format") plus scope (filtered list). It also names the sibling it differs from (invoices_export_zip) and implicitly from invoices_list, so an agent can select it without opening another schema.

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?

Explicitly says it accepts the same filters as invoices_list, giving the agent a reference for filter semantics. It also supplies a concrete routing rule: above 10,000 invoices or when files are needed, use invoices_export_zip.

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