Skip to main content
Glama

lordo_netto_irpef_simulator

Read-onlyIdempotent

[Deterministic Italian tax simulation. Pure calculation, read-only, side-effect free]. Simulates employee net take-home salary from Gross Annual Salary (RAL) under post-reform 3-tier IRPEF brackets (23%, 35%, 43%), TUIR employment tax credits (detrazioni lavoro dipendente), statutory IVS social security employee cuts (cuneo fiscale), and regional/municipal surcharges across Italian regions. Usage: Use this tool to compute worker monthly net pay in Italy. Do NOT use for employer-side total company employment cost (use 'costo_aziendale_dipendente' instead). Returns: JSON object with { ralEur: number, netAnnualSalaryEur: number, netMonthlySalaryEur: number, monthlyInstallmentsCount: number, grossIrpefEur: number, netIrpefEur: number, employeeInpsDeductionEur: number, regionalSurchargeEur: number, municipalSurchargeEur: number, effectiveTaxRatePercent: number }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lordo_netto_irpef_simulator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ralEurNoAlias for grossAnnualSalaryEur in EUR
regioneNoItalian alias for italianRegion
monthsCountNoNumber of salary months (13 or 14)
italianRegionNoItalian administrative region for regional surcharge (e.g. Lombardia, Lazio, Veneto)Lombardia
numeroMensilitaNoItalian alias for monthsCount (13 or 14)
grossAnnualSalaryEurNoGross annual salary (RAL) in EUR (e.g. 32000)
applyTaxWedgeReductionNoWhether statutory IVS tax wedge reduction applies (cuneo fiscale)
municipalTaxRatePercentNoMunicipal surcharge rate percentage (default: 0.8%)
applicaTaglioCuneoFiscaleNoItalian alias for applyTaxWedgeReduction
aliquotaAddizionaleComunalePercentNoItalian alias for municipalTaxRatePercent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's "Pure calculation, read-only, side-effect free" restates structured data rather than adding to it. The one genuinely additive behavioral claim is "Deterministic", which signals stable output for identical inputs and is not covered by any annotation. It does not discuss alias precedence when both English and Italian parameter forms are supplied, which is the main behavioral risk for this tool.

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 definition is front-loaded and segmented into bracketed scope, 'Usage', and 'Returns', so an agent can scan it quickly. The opening clause is somewhat redundant against the read-only/idempotent annotations, and the tax-rule enumeration is dense, but no sentence is wasted given the domain complexity.

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?

There is no output schema, and the description compensates by listing the eleven returned fields (ralEur, netMonthlySalaryEur, grossIrpefEur, employeeInpsDeductionEur, effectiveTaxRatePercent, etc.), which is exactly what an agent needs to consume the result. The remaining gap is the absence of any guidance on the ten-parameter alias duplication and whether Italian or English forms take precedence.

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 description coverage is 100%, so the schema already documents all 10 parameters including aliases, defaults (Lombardia, 0.8%, applyTaxWedgeReduction=true), and the 13/14 month constraint. The description only gestures at RAL, regions, and surcharges conceptually, and never explains how the duplicated alias pairs (ralEur/grossAnnualSalaryEur, regione/italianRegion, monthsCount/numeroMensilita, etc.) interact. Baseline 3 is appropriate when the schema carries the load.

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 names a specific verb and resource ("Simulates employee net take-home salary from Gross Annual Salary (RAL)") and enumerates the exact rule sets modeled: 3-tier IRPEF brackets, TUIR detrazioni, IVS cuneo fiscale, and regional/municipal surcharges. It explicitly distinguishes itself from the sibling 'costo_aziendale_dipendente', so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Usage' section states the positive case (compute worker monthly net pay in Italy) and the exclusion with a named alternative: "Do NOT use for employer-side total company employment cost (use 'costo_aziendale_dipendente' instead)." Both the when and the when-not are explicit, leaving nothing to inference.

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.

Resources