Skip to main content
Glama

ItaliaTools

by dev.workers.italiatools.italiatools

calcola_crypto_tax

Calcola le tasse sulle criptovalute per il 2026: imposta sostitutiva 33% sulle plusvalenze (26% per stablecoin EUR MiCA-compliant) e IVCA 0,2% sul valore del portafoglio al 31/12. Franchigia €2.000 abolita dal 2026. Fonte: Art. 67 TUIR, L. 207/2024 art. 1 commi 24-29.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plusvalenzaYesPlusvalenza netta realizzata nell'anno in euro. Può essere 0 o negativo (minusvalenza). Es: 10000
portafoglioYesValore totale del portafoglio crypto al 31 dicembre dell'anno in euro (base per IVCA). Es: 50000
tipo_criptoNoTipo di criptovaluta: ordinaria (BTC, ETH, altcoin) → aliquota 33%; stablecoin_eur (es. EURC, MiCA-compliant) → aliquota 26%.
minusvalenze_pregresseNoMinusvalenze non compensate da anni precedenti in euro (default: 0). Riportabili per 4 anni (Art. 68 co.9-bis TUIR).

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It transparently discloses tax rates, the abolition of the €2,000 exemption, and legal sources, but does not describe the return format or what happens with negative values (minusvalenze). While useful, it omits some behavioral aspects like how the calculation is 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 a single dense sentence that packs a lot of useful information without being bloated. It is front-loaded with the purpose and then provides essential details. A minor improvement would be to split into two sentences for readability, but it remains efficient.

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 no output schema and no annotations, the description provides a solid overview including tax rates, threshold changes, and legal references. However, it does not mention what the tool returns (e.g., breakdown of taxes, total amount) or handle edge cases, so there is a slight gap for a calculation tool with no structured output documentation.

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 schema already provides 100% coverage for all four parameters, including clear descriptions and examples. The description adds some value by explaining the IVCA basis for the portafoglio parameter and the 4-year carryforward for minusvalenze, but it mostly reiterates what the schema already states.

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 a specific verb 'calcola' (calculates) and clearly identifies the resource: crypto taxes for 2026, with specific tax rates. It clearly distinguishes from sibling tools which cover other Italian tax topics (IRPEF, INPS, flat-rate scheme).

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 explicitly states the context (tax calculation for crypto in 2026) and provides regulatory details, making it clear when to use this tool. It does not explicitly mention alternatives, but the sibling tool names make the distinction obvious, and the detailed tax rules imply a niche focus.

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

All ItaliaTools 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/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