Skip to main content
Glama
stornoro

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

anaf_declaration_status

Read-onlyIdempotent

Check the processing status of an ANAF declaration by upload index and taxpayer CUI/CNP, returning accepted, validation-error, processing, or unknown state and the recipisa PDF URL when available.

Instructions

Processing status of a declaration filed on the ANAF e-guvernare portal (after agent_submit_declaration_pdf or any upload that returned an index): ANAF's public StareD112 by upload index and the taxpayer's CUI/CNP. States: ok (accepted), nok (validation errors, see recipisa), processing, unknown (not indexed yet). Storno asks the three StareD112 hosts in turn (www.anaf.ro, stare.anaf.ro, epatrim.anaf.ro), so an outage of one does not hide the state. Returns the recipisa PDF URL when available. Public, no account.

Input Schema

NameRequiredDescriptionDefault
cuiYesCUI or CNP the declaration was filed for
indexYesUpload index returned by the portal, or the registration number from the counter (with ghiseu: true)
ghiseuNotrue when the number is the registration number given at the ANAF counter, not an online upload index

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.48
    • addedInput schema / properties / ghiseu
      Added value: +{
+  "description": "true when the number is the registration number given at the ANAF counter, not an online upload index",
+  "type": "boolean"
+}
    • changedInput schema / properties / index / description
      Previous value: -"Upload index returned by the portal"New value: +"Upload index returned by the portal, or the registration number from the counter (with ghiseu: true)"
  2. Addedv1.0.28

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it explains the host fallback behavior across three StareD112 hosts, the meaning of each status value, and that it returns the recipisa PDF URL when available. It also clarifies that the service is public and needs no account.

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 front-loaded with the core purpose and then adds only useful operational context: status meanings, host fallback, and the recipisa return. There is no filler, and the single dense sentence remains readable.

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?

With no output schema, the description still explains the possible statuses and the optional recipisa PDF URL. Combined with complete parameter coverage and annotations, it gives the agent enough context to call and interpret the tool 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 coverage is 100%, so the parameter meanings are already documented in the schema. The description reinforces that the index is the upload index and that CUI/CNP identifies the taxpayer, but it does not add materially new parameter semantics, so baseline 3 is appropriate.

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 names a specific operation and resource: checking ANAF declaration processing status via StareD112 using an upload index and CUI/CNP. It also ties the tool to the preceding upload/submission action, making it easy to distinguish from general declaration 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?

It clearly states when to use the tool: after agent_submit_declaration_pdf or any upload that returned an index. It does not explicitly name alternatives or when-not conditions, but the triggering context 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