Skip to main content
Glama

NovaPixel LexGrid

lordo_netto_irpef_simulator

Simulates Italian net take-home salary under post-reform 3-tier IRPEF, TUIR deductions, employee IVS contribution cuts, and regional/municipal surcharges.

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
regioneNoAlias for italianRegion
monthsCountNoNumber of salary months (13 or 14)
italianRegionNoItalian administrative region for regional surchargeLombardia
numeroMensilitaNoAlias for monthsCount
grossAnnualSalaryEurNoGross annual salary (RAL) in EUR
applyTaxWedgeReductionNoWhether statutory IVS tax wedge reduction applies
municipalTaxRatePercentNoMunicipal surcharge rate percentage
applicaTaglioCuneoFiscaleNoAlias for applyTaxWedgeReduction
aliquotaAddizionaleComunalePercentNoAlias for municipalTaxRatePercent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the substantive modeling assumptions (post-reform IRPEF tiers, TUIR deductions, IVS wedge reduction, surcharges), which is real behavioral value. However, it never states that this is a side-effect-free calculation, nor how defaults (Lombardia region, wedge reduction on) or alias pairs are resolved.

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?

A single dense sentence with the resource and scope front-loaded and zero filler. It is slightly over-packed (four tax-domain clauses in one sentence) but every clause 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?

For a 10-parameter simulation tool with no required parameters and no output schema, the description should say what happens with an empty call, which defaults apply, and what the result looks like. None of that is covered, leaving meaningful gaps an agent would need before invoking it confidently.

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 each parameter is already documented in the schema, giving a baseline of 3. The description adds no parameter-level meaning, and notably does not explain how the duplicated English/Italian alias pairs (ralEur vs grossAnnualSalaryEur, regione vs italianRegion) are prioritized if both are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Simulates') and a specific resource ('Italian net take-home salary') and even enumerates the calculation components (post-reform 3-tier IRPEF, TUIR deductions, IVS cuts, regional/municipal surcharges). It is clearly distinguishable from siblings like costo_aziendale_dipendente (employer cost) by scope, though it does not explicitly name an alternative.

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

Usage Guidelines2/5

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

The description says only what the tool computes; there is no guidance on when to choose it, when not to, or how it relates to the other payroll tools. The agent must infer usage purely from the purpose statement.

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