Skip to main content
Glama
cmendezs

mcp-fattura-elettronica-it

validate_cessionario

Validate and prepare buyer data for Italian e-invoicing: ensure correct tax IDs and name fields. Returns CessionarioCommittente block or errors.

Instructions

Validate and build the CessionarioCommittente (buyer) block for FatturaPA.

Use this as step 5 in the invoice generation workflow, after validate_cedente_prestatore() and before build_dati_generali().

Validates: either denominazione or both nome+cognome must be provided (mutually exclusive); at least one tax identifier (id_codice with id_paese, or codice_fiscale) is required; id_codice requires id_paese to be set.

Italian B2C buyers with only a CodiceFiscale: set codice_fiscale and leave id_paese/id_codice empty. Foreign B2B buyers: set id_paese + id_codice.

On success returns {'CessionarioCommittente': {...}} ready for generate_fattura_xml(). On failure returns {'error': ''} listing all issues joined by '; '.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
denominazioneNoCompany name of the buyer. Mutually exclusive with nome+cognome.
nomeNoFirst name of the buyer (natural person).
cognomeNoLast name of the buyer (natural person).
id_paeseNoISO country code for IdFiscaleIVA. Required for VAT-registered buyers. Omit for Italian buyers identified only by CodiceFiscale.
id_codiceNoVAT number of the buyer. Required if id_paese is provided.
codice_fiscaleNoItalian fiscal code (16-char alphanumeric for individuals, 11-digit numeric for companies). Alternative to IdFiscaleIVA.
indirizzoNoStreet address of the buyer.
capNoPostal code of the buyer.
comuneNoCity of the buyer.
nazioneNoISO country code of the buyer.IT

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Details validation rules (mutual exclusivity, tax identifier requirements) and describes both success and error return formats, including that errors list all issues joined by '; '. No annotations provided, so description carries full burden and does so thoroughly.

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?

Description is efficiently structured: first sentence states purpose, second gives workflow step, then validation rules, special cases, and return values. No unnecessary words, well front-loaded.

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?

Given 10 parameters, complex rules, and an existing output schema, the description covers validation, workflow placement, return format, and edge cases. It is complete for the agent to correctly select and invoke the tool.

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 description coverage is 100%, providing clear per-parameter descriptions. The tool description adds value by explaining the validation logic and rules for when to use combinations, enhancing understanding 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 clearly states it validates and builds the CessionarioCommittente block for FatturaPA, and positions it as step 5 in the workflow, distinguishing it from sibling tools like validate_cedente_prestatore and build_dati_generali.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly orders usage: after validate_cedente_prestatore() and before build_dati_generali(). Also provides specific rules for Italian B2C versus foreign B2B buyers, guiding when to use which parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cmendezs/mcp-fattura-elettronica-it'

If you have feedback or need assistance with the MCP directory API, please join our Discord server