Skip to main content
Glama

costo_aziendale_dipendente

Read-onlyIdempotent

[Deterministic Italian payroll calculation. Pure calculation, read-only, side-effect free]. Calculates the full employer-side total labor cost (Costo Aziendale): Gross Annual Salary (RAL), employer INPS social security contributions (~24%), INAIL occupational accident insurance premium, annual TFR severance accrual (Art. 2120 Codice Civile), and real net hourly employment cost across 13 or 14 months. Usage: Use this tool to evaluate total corporate cost for hiring or retaining an employee in Italy. Do NOT use for employee take-home net pay simulation (use 'lordo_netto_irpef_simulator' instead). Returns: JSON object with { ralEur: number, inpsEmployerEur: number, inailPremiumEur: number, tfrAccrualEur: number, totalCompanyCostEur: number, monthlyCostEur: number, hourlyCostEur: number, assumptions: object }.

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

Input Schema

NameRequiredDescriptionDefault
ralEurNoAlias for grossAnnualSalaryEur in EUR
atecoSectorNoItalian ATECO macro-industry sector for INPS/INAIL rates
monthsCountNoNumber of salary months (13 for 13th month bonus, 14 for 13th+14th)
settoreAtecoNoItalian alias for atecoSector
numeroMensilitaNoItalian alias for monthsCount (13 or 14)
inailTassoPerMilleNoItalian alias for inailRatePerThousand
grossAnnualSalaryEurNoGross annual salary (RAL) in EUR (e.g. 35000)
inailRatePerThousandNoINAIL occupational safety rate per thousand (e.g. 4.0 for commerce, 12.0 for manufacturing)
applicaEsoneroUnder36NoItalian alias for applyYouthIncentiveUnder36
applyYouthIncentiveUnder36NoWhether statutory youth/women hiring incentive exemption applies

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so 'pure calculation, read-only, side-effect free' largely restates them. Beyond that, the description adds genuinely non-structured context: the ~24% INPS approximation, the Art. 2120 legal basis for TFR, and the presence of an 'assumptions' object flagging that results are deterministic but estimate-based. No contradiction with annotations.

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?

Well structured and front-loaded: bracketed properties first, then Usage, then Returns, so an agent can skim to the routing sentence. Minor waste in the bracketed preamble, which duplicates the readOnly/idempotent annotations rather than adding new information.

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?

With no output schema and 10 parameters, the description compensates by inlining the return object's fields (ralEur, inpsEmployerEur, inailPremiumEur, tfrAccrualEur, totalCompanyCostEur, monthlyCostEur, hourlyCostEur, assumptions). That is enough for an agent to call the tool and interpret results; only the alias/incentive parameters and the zero-required-parameter behavior are left unexplained.

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 one of the 10 parameters is already documented, including both the Italian and English alias pairs. The description only touches parameter space indirectly via '13 or 14 months' and the INPS/INAIL component names; it adds no meaning about the alias duplication, the ATECO sector enum values, or the youth-incentive flag, so the baseline 3 applies.

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?

States a specific verb and resource — 'Calculates the full employer-side total labor cost (Costo Aziendale)' — and enumerates the exact components (RAL, INPS ~24%, INAIL, TFR Art. 2120, hourly cost). It also names the sibling lordo_netto_irpef_simulator as the tool it is not, so an agent can discriminate 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?

Explicit routing guidance: 'Use this tool to evaluate total corporate cost for hiring or retaining an employee in Italy' paired with an explicit exclusion, 'Do NOT use for employee take-home net pay simulation (use lordo_netto_irpef_simulator instead)'. Both the when and the when-not are given, along with the alternative to select.

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