Skip to main content
Glama

Italy Salary and Income Tax Calculator

Employer cost of a salary in Italy

employer_cost
Read-onlyIdempotent

What a salary in Italy costs the employer (employer social contributions itemised), or the reverse: the gross salary a total budget allows. Give gross_annual or budget_annual.

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": "employer_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoRegion: lombardy = Lombardy (Milan); lazio = Lazio (Rome); piedmont = Piedmont (Turin); veneto = Veneto (Venice, Verona); tuscany = Tuscany (Florence); campania = Campania (Naples). Default lombardy.
marriedNoMarried or registered partner. Default false.
childrenNoNumber of dependent children. Default 0.
municipalNoMunicipal surtax rate. Milan 0.8%, Rome 0.9%. Set by each comune. (%). Default 0.8.
impatriatiNoImpatriati regime (new resident) Default false.
pension_pctNoVoluntary employee pension contribution through payroll, % of salary. Default 0.
bonus_annualNoYearly bonus in EUR. Default 0.
gross_annualNoGross yearly salary in EUR
budget_annualNoTotal yearly employer budget in EUR, to find the gross salary it allows
spouse_incomeNoPartner's gross yearly income in EUR, for joint taxation and spouse allowances. Default 0.
municipal_exemptNoMunicipal exemption up to (€). Default 23000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that employer social contributions are itemised in the output, which is useful beyond the annotations, but it says nothing about rate assumptions, sensitivity to region/municipal inputs, or the shape of the reverse-mode result.

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?

Two sentences with no waste: the primary purpose and itemised output come first, the reverse mode second, and the input-selection rule last. 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?

With 11 parameters, no required fields and no output schema, the description leaves return values largely unexplained — only 'social contributions itemised' hints at the response, and nothing describes what the budget-mode result contains. Error/validation behavior when conflicting inputs are given is also unaddressed.

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 every parameter is already documented with defaults and meaning. The description's only semantic addition is the gross_annual/budget_annual mutual exclusivity, which is genuinely helpful but minimal. Baseline 3 is appropriate.

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?

The description names the specific resource (employer cost of a salary in Italy) and both computation directions: salary → employer cost, and budget → gross salary. That clearly separates it from net_salary and gross_for_target_net, though it never names those siblings explicitly.

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?

'Give gross_annual or budget_annual' tells the agent that exactly one of two inputs selects the mode, which is real usage guidance. However, there is no statement of when to prefer this over sibling tools (net_salary, gross_for_target_net, compare_with_netherlands) and no note about what happens if both or neither are supplied.

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