Skip to main content
Glama
gsaccardi

Dichiarino

by gsaccardi
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

calcola_addizionale_regionale_tool

Calculate the regional IRPEF surtax for any Italian region. Input total income and region to get the tax amount owed for a specific tax year.

Instructions

Calcola l'addizionale regionale IRPEF per una specifica regione.

    L'addizionale regionale è un'imposta separata dall'IRPEF, trattenuta dal
    sostituto d'imposta e conguagliata nella dichiarazione.

    Args:
        reddito_complessivo: Reddito complessivo in euro.
        regione: Nome della regione (es. "lombardia", "lazio", "campania").
        anno: Anno di imposta. Default: 2024.

    Regioni disponibili:
        abruzzo, basilicata, calabria, campania, emilia_romagna,
        friuli_venezia_giulia, lazio, liguria, lombardia, marche, molise,
        piemonte, puglia, sardegna, sicilia, toscana, trentino_alto_adige,
        umbria, valle_d_aosta, veneto

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annoNo
regioneYes
reddito_complessivoYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only describes the tax concept and lists available regions, without stating side effects, error handling, or limitations. There is no indication of what happens with invalid inputs or how results are returned.

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 well-structured with a clear opening sentence, a brief background paragraph, and organized Args and region lists. The background paragraph adds domain context but could be trimmed; overall, it earns its place.

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?

The description covers the main inputs and lists available regions, which is helpful. However, the default year discrepancy and lack of error-handling details leave some ambiguity. Since an output schema exists, return values are not required in the description.

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 description includes an Args section explaining each parameter's meaning and lists available region values, compensating for the schema's lack of descriptions. However, it incorrectly states the default for anno as 2024 while the schema specifies 2025, creating conflicting guidance.

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 first sentence clearly states the tool calculates the regional IRPEF surcharge for a specific region, using the verb 'Calcola' and identifying the resource 'addizionale regionale IRPEF'. This distinguishes it from sibling tools like calcola_irpef.

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?

Provides context about the tax being separate from IRPEF and retained by the withholding agent, but does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria. Usage is implied by the tool's name and sibling set, but no explicit guidance is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gsaccardi/dichiarino-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server