Skip to main content
Glama
stornoro

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

declarations_update

Idempotent

Update a draft declaration's data or metadata, or record a filing made outside Storno so its ANAF state is tracked. Only drafts can be edited.

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

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.1/5.0
Behavior4/5

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

Annotations already mark it as non-read-only, idempotent and non-destructive; the description adds the important constraint that editing is limited to drafts and discloses a real side effect — with `filedExternally` Storno records an external filing and tracks its state on StareD112. That is behavior an agent could not infer from the annotations.

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?

Two dense sentences, front-loaded with the action and the editable fields, followed by the status constraint and the external-filing exception. No filler; every clause carries a rule the agent needs.

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 5-parameter mutation tool with no output schema, the description covers the mutable payload, the draft precondition, and the external-filing side effect. It does not say whether omitted fields are preserved or how the response reports the new state, which is the main remaining gap.

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?

Schema coverage is 60%, and the description compensates by explaining the shape of `data` (form input under data.input, attachments under data.attachments for d212/c168) and by spelling out the `filedExternally` index/ghiseu semantics. `metadata` and `companyId` remain thin, but the two opaque parameters are covered well.

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 ('Update a draft declaration') and immediately scopes the editable surface to `data` and/or `metadata`, which distinguishes it from declarations_create and declarations_submit. It does not name a sibling explicitly, but the draft-only constraint effectively separates it from the submit/validate tools.

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?

Explicitly states 'Only drafts can be edited', which is the key precondition an agent needs, and clarifies that `filedExternally` is valid in any status but submitted/accepted. No named alternatives, but the usage envelope is unambiguous.

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