Skip to main content
Glama
stornoro

Storno CLI

by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

declarations_update

Update draft declarations by modifying form data, attachments, or metadata. Also record filings made outside Storno to track their status.

Instructions

Update a draft declaration: data (for d212 / c168 the form input under data.input and attachments under data.attachments) and/or metadata. Only drafts can be edited. With filedExternally (any status but submitted/accepted) Storno records a filing made outside it and follows its state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDeclaration UUID
dataNo
metadataNo
companyIdNoCompany UUID (overrides STORNO_COMPANY_ID env var)
filedExternallyNoThe declaration was filed outside Storno (portal by hand, another program, at the counter): Storno records ANAF's number and follows its state on StareD112; ghiseu: true when the number is the counter registration number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.48
    • addedInput schema / properties / filedExternally
      Added value: +{
+  "additionalProperties": false,
+  "description": "The declaration was filed outside Storno (portal by hand, another program, at the counter): Storno records ANAF's number and follows its state on StareD112; ghiseu: true when the number is the counter registration number",
+  "properties": {
+    "ghiseu": {
+      "type": "boolean"
+    },
+    "index": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "index"
+  ],
+  "type": "object"
+}
  2. Addedv1.0.37

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries full responsibility. It discloses that only drafts can be edited and explains the filedExternally behavior (recording an external filing and following its state). However, it does not clarify whether the update is a merge or full replacement of the data object, nor does it mention side effects like validation, status changes, or response contents. This is a moderate gap for a mutation tool.

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 two sentences, front-loaded with the core action ('Update a draft declaration'), followed by precise constraints and special-case behavior. No filler or repetition; every clause adds value. This is exemplary conciseness for a tool of this complexity.

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 an update operation with nested objects and no output schema, the description covers the essential purpose, constraints, and a special workflow. It lacks explicit mention of return values or error behavior, but given the complexity and schema descriptions, it is reasonably complete. The missing merge semantics could be considered a gap, but overall it is adequate.

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?

The description adds meaningful context for the 'data' parameter by explaining its internal structure for d212/c168 (data.input and data.attachments), which is not evident from the schema alone. It also gives extra context for 'filedExternally'. Given a 60% schema coverage, the description partially compensates for the undocumented parameters, but does not fully explain all (e.g., companyId override).

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 clearly states the tool updates a draft declaration, specifying the updatable fields (data and metadata) and the target status (drafts only). It distinguishes itself from related tools like declarations_create or declarations_submit by the action and constraints. The mention of 'filedExternally' adds a unique use case, making the purpose unambiguous.

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?

It explicitly states 'Only drafts can be edited', providing a clear condition for when to use this tool. It also describes the filedExternally scenario, indicating a specific workflow. However, it does not explicitly name alternatives (e.g., declarations_create for new declarations) or provide explicit 'when not to use' guidance beyond the draft restriction, so it is slightly below perfect.

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