Skip to main content
Glama

Imperio — Italian Tax & Compliance Tools

by com.imperioutils
OverviewDiscussionsAdmin

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 agevolata 5% per le nuove attività: vale per l'anno di inizio e per i quattro successivi (default false → 15%). Non cambia gli acconti: nel primo anno di attività non sono dovuti, e le note della risposta lo dicono.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / startup / description
      Previous value: -"Aliquota startup 5% per i primi 5 anni (default false → 15%)."New value: +"Aliquota agevolata 5% per le nuove attività: vale per l'anno di inizio e per i quattro successivi (default false → 15%). Non cambia gli acconti: nel primo anno di attività non sono dovuti, e le note della risposta lo dicono."
  2. Changed3 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "ateco"
+    ]
+  },
+  {
+    "required": [
+      "coefficiente"
+    ]
+  }
+]
    • changedInput schema / properties / ateco / description
      Previous value: -"Codice ATECO per derivare il coefficiente di redditività (opzionale)."New value: +"Codice 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'»)."
    • changedInput schema / properties / coefficiente / description
      Previous value: -"Coefficiente di redditività in % (override manuale, opzionale)."New value: +"Coefficiente di redditività in % (override manuale). ALTERNATIVO ad `ateco`: uno dei due è obbligatorio."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new traits: it is free (€0), deterministic, and requires no login, which speaks to auth needs and result stability. It stops short of describing the return format, but that is minor for a pure calculator.

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?

Two tight sentences, front-loaded with what the tool computes before the softer marketing traits. Minor redundancy in 'Gratis (€0)' where €0 merely restates Gratis, but overall it wastes little.

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

Completeness3/5

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

With no output schema, the description carries the burden of describing results, and while it names the outputs (imposta sostitutiva, contributi INPS), it gives no sense of the returned structure or fields. For a moderately complex 7-parameter tax calculation, that leaves a gap, though the rich schema offsets it somewhat.

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 coverage is 100%, so the schema already documents all 7 parameters, including the ateco/coefficiente alternation and the startup/riduzione_35 flags. The description only restates the fatturato and ATECO inputs and adds no syntax or constraint detail beyond the schema, matching the baseline of 3.

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?

States a specific verb (Calcola) and resource (imposta sostitutiva e contributi INPS del regime forfettario italiano) and names the input basis (fatturato, opzionale codice ATECO). This clearly distinguishes it from sibling calculators such as calc_iva, calc_imu, or calc_reverse_charge, each of which targets a different regime/tax.

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 scope (regime forfettario) implies when to use it, and the parenthetical 'opzionale codice ATECO' hints at the input model, but there is no explicit when/when-not guidance or reference to alternatives among the many calc_* siblings. Usage must be inferred from the regime name.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources