Skip to main content
Glama

Imperio — Italian Tax & Compliance Tools

by com.imperioutils

Calcola IMU

calc_imu
Read-onlyIdempotent

Calcola l'IMU italiana (L.160/2019) per fabbricati (da rendita catastale + categoria), terreni agricoli (da reddito dominicale) e aree edificabili (da valore venale), con acconto/saldo. L'aliquota (‰) è quella deliberata dal Comune. Gratis (€0), deterministico, nessun login richiesto.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detrazioneNoDetrazione in euro (solo fabbricati; es. 200 per abitazione principale di lusso).
mesi_possessoNoMesi di possesso nell'anno (default 12).
tipo_immobileNoTipo immobile → seleziona la formula (default abitazione_non_principale).
valore_venaleNoAree edificabili: valore venale in comune commercio al 1° gennaio (€). OBBLIGATORIO con `tipo_immobile: area_edificabile`.
aliquota_permilleYesAliquota deliberata dal Comune, in per mille (es. 8.6 per 8,6‰).
rendita_catastaleNoFabbricati: rendita catastale annua in euro (da visura). OBBLIGATORIA per tutti i tipi diversi da `terreno_agricolo` e `area_edificabile` — cioè anche per il tipo di default `abitazione_non_principale`.
quota_possesso_pctNoQuota di possesso in % (default 100).
reddito_dominicaleNoTerreni agricoli: reddito dominicale da visura (base = ×1,25×135). OBBLIGATORIO con `tipo_immobile: terreno_agricolo`, tranne quando il terreno è esente (vedi i due flag).
categoria_catastaleNoCategoria catastale per i fabbricati (default A). Determina il moltiplicatore.
esente_montano_isolaNoTerreni: in comune montano/collinare o isola minore → esente.
coltivatore_diretto_iapNoTerreni: coltivatore diretto/IAP iscritto alla previdenza agricola → esente.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context: free (€0), deterministic, and no login required. It does not describe the output format, but this is a minor gap given the strong annotation coverage.

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 two sentences and packs all key facts: purpose, supported use cases, rate source, and behavioral traits. It is front-loaded with the verb and resource, and there is no redundant or filler 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?

Despite the absence of an output schema, the description explains the core calculation scope and legal reference. The schema fills in parameter details. A minor gap is the lack of any statement about what the tool returns (e.g., amount in euros, breakdown), but overall the context is sufficient for a complex 11-parameter calculator.

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%, and each parameter already has detailed descriptions (e.g., aliquota_permille, rendita_catastale, conditional requirements). The tool description adds only high-level category info and the legal basis, which does not materially go beyond the schema's parameter documentation.

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 opens with a specific verb and resource: 'Calcola l'IMU italiana' and enumerates the exact property categories (fabbricati, terreni agricoli, aree edificabili). This clearly differentiates it from sibling calculators like calc_iva or calc_forfettario.

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?

The description gives clear context for when to use the tool: for Italian IMU calculation with specific property types and the municipality rate. It does not explicitly name alternatives or exclusions, but the context is unambiguous enough for an agent to select it over sibling tax tools.

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

All Imperio — Italian Tax & Compliance Tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Tools are mostly distinct, targeting specific tax/compliance operations. The pair 'parse_fatturapa' and 'parse_verify_fatturapa' are similar but differentiated by the verification step. The detailed descriptions further reduce ambiguity.

Naming Consistency4/5

Names follow a consistent verb_noun pattern with prefixes like 'calc_', 'validate_', 'lookup_', 'parse_', 'nis2_', etc. Minor deviations exist (e.g., 'compose_f24' vs 'calc_forfettario', 'intrastat_compose' vs 'intrastat_periodicity') but overall the pattern is clear.

Tool Count3/5

With 23 tools, the set is on the heavier side for a single server, covering many subdomains of Italian tax and compliance. While each tool seems purposeful, the count exceeds the typical well-scoped range (3-15), making it slightly overwhelming.

Completeness4/5

The tool surface covers a wide array of Italian tax and compliance needs: tax calculations, F24 composition, INTRASTAT, ATECO, NIS2, FatturaPA, and validations. Minor gaps exist (e.g., no IRPEF or IRAP calculators), but the core tax workflows are well supported.

Resources