Skip to main content
Glama

Imperio — Italian Tax & Compliance Tools

by com.imperioutils

Calcolatore Regime Forfettario

calc_forfettario
Read-onlyIdempotent

Calcola imposta sostitutiva e contributi INPS del regime forfettario italiano dal fatturato e (opzionale) codice ATECO. Gratis (€0), deterministico, nessun login richiesto.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atecoNoCodice ATECO da cui derivare il coefficiente di redditività. ALTERNATIVO a `coefficiente`: uno dei due è obbligatorio (senza, il calcolo non ha coefficiente e il tool risponde «Fornire 'ateco' oppure 'coefficiente'»).
ricaviYesRicavi/compensi annui in euro.
startupNoAliquota startup 5% per i primi 5 anni (default false → 15%).
coefficienteNoCoefficiente di redditività in % (override manuale). ALTERNATIVO ad `ateco`: uno dei due è obbligatorio.
riduzione_35NoRiduzione contributiva INPS del 35% (artigiani/commercianti).
gestione_inpsNoGestione previdenziale INPS/cassa (opzionale).
contributi_cassa_privataNoContributi cassa privata già versati, in euro (opzionale).

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool is 'Gratis (€0), deterministico, nessun login richiesto', which provides extra behavioral context beyond the annotations. However, it does not describe output format or edge-case behavior, so it offers modest added value.

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 a single sentence defining the main purpose, followed by a short second sentence with practical attributes (free, deterministic, no login). It is front-loaded and contains no filler or redundant information.

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?

Given the rich schema descriptions and strong annotations, the description is largely complete for a calculator tool. It states what is computed and key usage constraints (free, no login), though it does not detail the exact output structure, which is not provided by an output schema.

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?

All 7 parameters have complete descriptions in the schema (100% coverage), so the baseline is 3. The description merely restates that the tool uses 'fatturato' and 'codice ATECO' without adding new parameter 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 uses the specific verb 'calcola' and clearly identifies the resource (imposta sostitutiva e contributi INPS) within the Italian regime forfettario. It also mentions the key inputs (fatturato, codice ATECO), which differentiates it from sibling calculators for other tax regimes.

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 description implies the tool is for regime forfettario calculations, but it does not explicitly state when to use it over alternatives like calc_iva or calc_imu, nor does it mention exclusions or prerequisites. Usage context is inferred from the name and mention of 'regime forfettario italiano', but no explicit alternative guidance is provided.

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