Skip to main content
Glama

calcola_irpef

Calcola IRPEF 2026 (lorda e netta) con detrazioni e addizionale regionale opzionale. Scaglioni: 23% fino a €28.000, 33% fino a €50.000, 43% oltre. Fonte: Art. 11 TUIR (DPR 917/1986), L. 207/2024.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
redditoYesReddito lordo annuo in euro (es: 35000)
regioneNoRegione per calcolo addizionale regionale (opzionale). Es: lombardia, lazio, campania, sicilia. Se omessa, viene restituito solo il range nazionale.
tipo_redditoYesTipo di reddito: dipendente (lavoro dipendente o pensione) oppure autonomo (partita IVA in regime ordinario)

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses the calculation includes deductions, optional regional surcharge, and specifically the 2026 tax brackets, along with its legal source. However, it does not explain behavior when 'regione' is omitted (though that is in the schema) or how output is structured, and since there are no annotations, the description carries the full burden. It also does not detail how deductions differ by tipo_reddito.

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: the first states function and scope, the second gives tax brackets and source. It is concise and front-loaded, with no redundant details.

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 description provides essential calculation context (tax brackets, year, legal basis) and states the output includes gross and net, which partially compensates for the lack of an output schema. However, it does not describe the return structure or behavior when the region is omitted, relying on the schema's regione description. Overall, it is fairly complete for a tax 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?

The input schema already covers all three parameters with descriptions and examples (reddito, regione, tipo_reddito), so the description adds minimal new information. The mention of 'addizionale regionale' and 'detrazioni' aligns with parameters but does not further clarify them. With 100% schema coverage, the baseline is 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?

The description clearly states the tool calculates IRPEF 2026 (gross and net) with deductions and optional regional surcharge. It provides the tax brackets and legal source, making the purpose unambiguous. This distinguishes it from sibling tools like calcola_forfettario or calcola_crypto_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 description implies usage for personal income tax calculation but does not explicitly mention when to use this tool over alternatives, such as calcola_forfettario for flat-rate regimes. It also does not state any exclusions or prerequisites. The context of sibling tools is available but not referenced.

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.

TDQS

A4/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific Italian fiscal or administrative calculation (e.g., codice fiscale, crypto tax, IRPEF) or information retrieval task (e.g., ATECO groups, fiscal news, deadlines), and their descriptions precisely define their scope without overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in Italian (e.g., calcola_codice_fiscale, lista_gruppi_ateco, novita_fiscali). The naming is uniform across all tools, using snake_case and descriptive terms that align with their functions, making them easily readable and predictable.

Tool Count5/5

With 9 tools, the count is well-scoped for the server's purpose of providing Italian fiscal and administrative tools. Each tool earns its place by covering key areas such as tax calculations, regulatory information, and deadlines, offering a comprehensive yet manageable set for agents to handle related tasks.

Completeness4/5

The tool set provides strong coverage for Italian fiscal calculations and information retrieval, including core tax types (e.g., IRPEF, INPS, forfettario), administrative codes, and regulatory updates. Minor gaps might exist, such as tools for specific deductions or advanced tax scenarios, but agents can likely work around these with the available tools for most common workflows.

Resources