Skip to main content
Glama
Sign In
Storno CLI

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

declarations_list

Read-onlyIdempotent

List tax declarations for the active company with filters by type, status, year, and month. Returns paginated results showing each declaration's status and period.

Instructions

List tax declarations for the active company. Supports filtering by type, status, year, and month. Returns paginated list of declarations with their status and period.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
typeNoDeclaration type filter
yearNoYear filter (e.g. 2026)
limitNoItems per page (default: 10, max: 20)
monthNoMonth filter (1–12)
statusNoStatus filter
companyIdNoCompany UUID (overrides STORNO_COMPANY_ID env var)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.48
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "d394",
-  "d300",
-  "d390",
-  "d100",
-  "d112"
-]New value: +[
+  "d394",
+  "d300",
+  "d390",
+  "d301",
+  "d398",
+  "d406",
+  "d100",
+  "d112"
+]
  2. First observedv1.0.17

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context: it scopes results to the active company and discloses that results are paginated and include status and period. It does not detail permissions or pagination metadata, but the annotation coverage lowers the burden.

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?

The description is three concise sentences and is front-loaded with the core purpose. Every sentence adds useful information about scope, filtering, and return shape.

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 list tool with no output schema, the description adequately explains that it returns a paginated list containing status and period. Combined with the fully documented input schema and safety annotations, an agent has enough information to invoke it correctly.

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 fully documents all seven parameters, including enums for type and status and ranges for year and month. The description names the main filters but does not add significant meaning 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?

The description uses a specific verb and resource: 'List tax declarations for the active company.' It also states the supported filters and return shape, which clearly distinguishes it from declaration detail tools like declarations_get.

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 usage is implied by 'List tax declarations' and the mentioned filters, but there is no explicit guidance on when to use this tool versus alternatives such as declarations_get or other declaration search/export tools.

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