Skip to main content
Glama
cmendezs

mcp-fattura-elettronica-it

lookup_codice_destinatario

Validate the format of an SDI recipient code or PEC address to determine the correct routing type for Italian e-invoicing and avoid transmission errors.

Instructions

Validate the format of a CodiceDestinatario (SDI recipient code) or PEC address.

Call this before build_transmission_header() to confirm the recipient routing type and that the code or PEC address is correctly formatted. At least one of codice or pec must be provided.

Routing rules:

  • codice is 6 alphanumeric chars (e.g. 'A1B2C3') → routing_type: 'SDI_CODE' (PA/IPA, FPA12)

  • codice is 7 alphanumeric chars (e.g. 'X1Y2Z3W') → routing_type: 'SDI_CODE' (B2B intermediary, FPR12)

  • codice is '0000000' (7 zeros) → routing_type: 'PEC'; pec_destinatario is then mandatory in build_transmission_header()

  • pec only (no codice) → validates email format, routing_type: 'PEC'

IPA note: 6-char PA office codes can be looked up at https://www.indicepa.gov.it. This tool performs format validation only — no live query against the SDI SOAP directory service or the IPA registry (planned for a future release).

On success returns a dict with 'routing_type', 'codice_destinatario' and/or 'pec_destinatario', and a 'note' with usage guidance. On invalid input returns {'error': ''}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codiceNoSDI CodiceDestinatario to look up: 6-char alphanumeric for PA offices (IPA code, FPA12 B2G invoices), 7-char alphanumeric for B2B intermediaries (FPR12), or '0000000' (7 zeros) for PEC routing. IPA codes can be verified at https://www.indicepa.gov.it.
pecNoPEC address to validate format (user@domain.ext). When a PEC is provided, CodiceDestinatario must be '0000000'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description fully discloses behavior: format validation only, no live query. Details return structure and error format, and notes future release for live query. Completely transparent.

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?

Well-structured with clear first sentence, bullet-like routing rules, and separate sections for notes and return description. Every sentence adds value without redundancy.

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 complexity of routing rules and presence of output schema, description covers all necessary aspects: usage context, parameter combinations, return values, and limitations (no live query). Complements structured fields effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds substantial meaning beyond schema: explains routing types per code length, provides examples, and clarifies dependencies between parameters (e.g., pec mandatory when codice '0000000').

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 the tool validates format of CodiceDestinatario or PEC address, with specific verb 'validate' and resource. It distinguishes from sibling tools like build_transmission_header (which uses the result) and provides detailed routing rules, making the purpose unambiguous.

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 advises to call before build_transmission_header() to confirm routing type and formatting. Includes routing rules and IPA lookup note, effectively guiding when and how to use the tool without needing alternatives.

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