declaration_form_spec
Retrieve the complete ANAF declaration form spec—JSON input schema, XML/XSD mapping, business rules, filing steps, and examples—to fill forms correctly before building.
Instructions
Everything needed to fill an ANAF declaration form correctly: the JSON input schema Storno expects (fields, required/optional, codes and their meaning, hints), how it maps to the ANAF XML (namespace, every XSD attribute with type and constraints), the business rules ANAF enforces (including the web-form rules the DUK validator misses, e.g. BR-C168-00991/0041/005911), the filing steps and a complete example. Read it before declaration_build. C168 addresses need the codes from anaf_nomenclator_*; never invent CNPs or CUIs.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"type": "<type>"
},
"name": "declaration_form_spec"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| xsd | No | true → return the raw ANAF XSD instead of the spec | |
| type | Yes | Form code, e.g. C168 |