Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

invoices_list

Read-onlyIdempotent

Retrieve paginated invoices for the active company with filtering by status, direction, date range, client, and search term, plus sorting and totals.

Instructions

List invoices for the active company with pagination, filtering, and sorting. Supports filtering by status (draft/issued/sent_to_provider/validated/rejected/cancelled), direction (incoming/outgoing), date range, client, and search term. Returns paginated results with totals.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sortNoField to sort by (default: issueDate)
limitNoItems per page, max 100 (default: 20)
orderNoSort order: asc or desc (default: desc)
dateToNoEnd date filter on the issue date, ISO 8601 (YYYY-MM-DD)
searchNoSearch term for invoice number or client name
statusNoFilter by invoice status
clientIdNoFilter by client UUID
dateFromNoStart date filter on the issue date, ISO 8601 (YYYY-MM-DD)
companyIdNoCompany UUID override (uses active company if not set)
directionNoFilter by direction: incoming or outgoing invoices

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.57
    • addedInput schema / properties / dateFrom
      Added value: +{
+  "description": "Start date filter on the issue date, ISO 8601 (YYYY-MM-DD)",
+  "type": "string"
+}
    • addedInput schema / properties / dateTo
      Added value: +{
+  "description": "End date filter on the issue date, ISO 8601 (YYYY-MM-DD)",
+  "type": "string"
+}
    • removedInput schema / properties / from
      Removed value: -{
-  "description": "Start date filter in ISO 8601 format (YYYY-MM-DD)",
-  "type": "string"
-}
    • removedInput schema / properties / to
      Removed value: -{
-  "description": "End date filter in ISO 8601 format (YYYY-MM-DD)",
-  "type": "string"
-}
  2. First observedv1.0.17

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the description focuses on behavior beyond safety: it states the active-company scope, supported filtering dimensions, pagination, sorting, and that results include totals. This adds useful operational context.

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 sentences, front-loaded with the core operation, then filters and return behavior. The text is dense but appropriate, with no filler or repetition.

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?

Given 11 optional parameters and no output schema, the description provides enough context to call the tool correctly: scope, filtering, pagination, sorting, and return summary. It could say more about the shape of returned totals, but is largely complete.

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 parameters including defaults and enum values. The description restates the main filter groups and enumerates status/direction values, but adds little syntax or meaning 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?

States a specific verb and resource (list invoices) with scope (active company) and capabilities (pagination, filtering, sorting). It is distinguishable from invoices_get by action, but 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 Guidelines3/5

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

Usage is implied by the list/filter nature of the tool, but the description does not explicitly say when to use it versus invoices_get, invoices_export_csv, or other invoice tools. No prerequisites or exclusions are stated.

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