Skip to main content
Glama
cmendezs

mcp-fattura-elettronica-it

by cmendezs
OverviewSchemaRelated ServersScoreDiscussions(1)
Python
Local

validate_cedente_prestatore

Builds and validates the seller (CedentePrestatore) block for FatturaPA invoices, enforcing Italian VAT and tax regime rules. Returns a ready-to-use XML object or a list of validation errors.

Instructions

Validate and build the CedentePrestatore (seller) block for FatturaPA.

Use this as step 4 in the invoice generation workflow, after build_transmission_header() and before validate_cessionario(). Call get_regime_fiscale_codes() first if you need to look up the RF code.

Gruppo IVA (VAT-group) sellers: when id_codice is a VAT-group IdFiscaleIVA, pass codice_fiscale set to the Codice Fiscale of the specific participating member company issuing this invoice, never the group's own CF. This mirrors the buyer-side rule enforced by SdI scarto code 00327 (see mcp_fattura_elettronica_it.sdi.notifications.SCARTO_CODE_REFERENCE); SdI does not publish an equivalent seller-side control code, but the same distinction applies structurally.

Validates: either denominazione or both nome+cognome must be provided (mutually exclusive); regime_fiscale must be a valid RF01–RF19 code; Italian Partita IVA (id_paese='IT') must be exactly 11 digits; codice_fiscale, if provided, must be 16 alphanumeric characters (individuals) or 11 digits (companies/VAT groups).

On success returns {'CedentePrestatore': {...}} ready to pass to generate_fattura_xml(). On failure returns {'error': ''} listing all validation issues joined by '; '.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoItalian postal code (5 digits) or foreign equivalent.
nomeNoFirst name (Nome), for individual sellers.
comuneNoCity/municipality of the registered office.
cognomeNoLast name (Cognome), for individual sellers.
nazioneNoISO 3166-1 two-letter country code of the registered office.IT
id_paeseYesISO 3166-1 two-letter country code of the seller (e.g. 'IT').
id_codiceYesPartita IVA (11 digits) or foreign VAT number of the seller.
indirizzoNoStreet address (via, piazza…) of the registered office.
denominazioneNoCompany name (Denominazione). Mutually exclusive with nome+cognome.
codice_fiscaleNoCodice Fiscale of the seller, optional. Set this when id_codice is a VAT-group (Gruppo IVA) IdFiscaleIVA: value must be the Codice Fiscale of the specific participating member company, never the group's own CF. Emitted as DatiAnagrafici/CodiceFiscale, between IdFiscaleIVA and Anagrafica per the XSD element order.
regime_fiscaleNoFiscal regime code RF01–RF19. Use get_regime_fiscale_codes() for the complete list. Most companies use RF01 (ordinary regime).RF01

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral burden. It discloses what is validated (denominazione vs nome+cognome, RF codes, Partita IVA length, codice_fiscale format), the Gruppo IVA participant-CF requirement, and the exact success and failure return shapes.

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 dense and front-loaded with the primary purpose, then workflow placement, then critical edge-case guidance, then return contract. Every major section serves a purpose, and the SdI reference adds real context without padding.

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?

For an 11-parameter validation tool with no annotations, the description covers purpose, workflow order, validation rules, the trickiest Gruppo IVA behavior, return values, and error shape. The schema covers field-level details, and the output schema/description covers the response contract. Nothing critical is missing.

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 100%, so the schema already documents each parameter. The description adds cross-parameter meaning beyond individual field docs, especially the Gruppo IVA rule for codice_fiscale and the exact 11-digit Partita IVA requirement when id_paese='IT', which is more than the baseline 3.

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 begins with a specific verb-resource pair: 'Validate and build the CedentePrestatore (seller) block for FatturaPA.' It is clearly distinguished from the sibling validate_cessionario by explicitly stating it is the seller-side block and positioning it in the workflow.

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?

The description gives an explicit workflow placement: step 4, after build_transmission_header() and before validate_cessionario(). It also instructs when to call get_regime_fiscale_codes() and identifies the buyer-side counterpart implicitly via the sibling name and step ordering.

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

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