Skip to main content
Glama

NovaPixel LexGrid

codice_fiscale_audit

Full bidirectional Italian Codice Fiscale audit: D.M. 23/12/1976 CIN check, reverse demographic extraction (gender, birthdate, Belfiore code), omocodia substitution detection & dehomocoding.

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": {
      "codiceFiscale": "<codiceFiscale>"
    },
    "name": "codice_fiscale_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
codiceFiscaleYes16-character alphanumeric personal Codice Fiscale or 11-digit legal entity code
expectedGenderNoExpected gender (M/F) for cross-check
expectedBirthDateNoExpected birth date in YYYY-MM-DD format for consistency check
expectedBelfioreCodeNoExpected Belfiore cadastral code (e.g. H501 for Roma, F205 for Milano)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the tool performs both forward (CIN) and reverse (gender, birthdate, Belfiore) processing plus omocodia substitution handling, which tells the agent what to expect from a single call. It stops short of describing how a failed CIN or mismatched expected value is surfaced, and does not state that the operation is a pure read-only computation.

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?

A single front-loaded sentence that leads with the overall capability and then lists the concrete checks, with zero filler. The domain jargon (D.M., CIN, Belfiore, omocodia) is dense but appropriate for the subject and a legal reference.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a moderate, self-contained computation with no annotations and no output schema, and the description compensates by naming every computation performed, which effectively previews the returned data. It leaves the concrete result shape (pass/fail fields, mismatch reporting) implicit, which is the main remaining gap.

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 description coverage is 100%, so all four parameters, including the M/F enum and the YYYY-MM-DD format, are already documented in structured fields. The description adds little parameter-level meaning beyond 'bidirectional'; it never mentions how the optional expectedGender/expectedBirthDate/expectedBelfioreCode cross-checks alter behavior.

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?

Names a specific verb (audit) and resource (Italian Codice Fiscale) and enumerates exactly what the audit covers: CIN check per D.M. 23/12/1976, reverse demographic extraction, and omocodia detection/dehomocoding. The domain is unmistakably different from the sibling tools (e-invoice XML, IBAN/SEPA, VIES/KYB), so an agent can route to it without opening the schema.

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

Usage Guidelines3/5

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

The word 'audit' plus the enumerated checks imply the tool is for validating or decoding a codice fiscale, but there is no explicit statement of when to use it or when another approach applies. No alternatives or preconditions (e.g. 'use before storing a tax code') are given; usage must be inferred from the purpose sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources