Skip to main content
Glama

codice_fiscale_audit

Read-onlyIdempotent

[Deterministic statutory audit. Pure calculation, read-only, side-effect free]. Full bidirectional Italian Codice Fiscale audit under D.M. 23/12/1976: mathematical CIN check character validation, reverse demographic extraction (gender, birthdate, Belfiore cadastral municipality code), omocodia substitution detection, and dehomocoding. Usage: Use this tool to audit 16-character Italian fiscal codes or decode demographic attributes. For VAT number verification and company KYB, use 'vies_gleif_kyb_verify' instead. Returns: JSON object with { isValid: boolean, isOmocodia: boolean, normalizedCf: string, demographics: { birthDate: string, gender: 'M' | 'F', belfioreCode: string, municipality: string }, cinValid: boolean }.

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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds real value beyond them: it asserts determinism ('Pure calculation, side-effect free') and grounds the logic in a named statute (D.M. 23/12/1976), which tells the agent results are reproducible and authoritative. It also discloses the return object shape (isValid, isOmocodia, normalizedCf, demographics, cinValid) even though no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is organized into three labeled blocks (scope preamble, Usage, Returns) and leads with the highest-value information, so an agent can skim it quickly. The bracketed preamble partly restates the read-only annotation, but it is short and the remainder is dense with useful content.

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?

For a four-parameter validation tool with no output schema, the definition covers purpose, alternative routing, and the full return field set, which is close to everything an agent needs. The only missing piece is what happens when an 11-digit legal entity code is supplied, which the schema permits but the description does not address.

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 the four parameters and the expected-value cross-checks are already documented in structured data. The description's mention of reverse demographic extraction (gender, birthdate, Belfiore code) loosely mirrors those parameters but adds no extra syntax, precedence, or mismatch-handling semantics 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 names a specific verb and resource ('Full bidirectional Italian Codice Fiscale audit') and then enumerates the concrete operations: CIN check character validation, reverse demographic extraction, omocodia substitution detection, and dehomocoding. It also names the sibling it is not for ('vies_gleif_kyb_verify' for VAT/KYB), so an agent can separate the two without opening either schema.

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

Usage Guidelines4/5

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

Explicit routing is provided: use this tool to audit 16-character fiscal codes or decode demographics, and use vies_gleif_kyb_verify for VAT number verification and company KYB. The one gap is that the schema allows an 11-digit legal entity code while the usage sentence only mentions 16-character personal codes, leaving the behavioral expectation for that input case unstated.

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