Skip to main content
Glama

transizione5_incentive_calculator

Read-onlyIdempotent

[Italian Piano Transizione 5.0 tax credit calculator. Deterministic calculation, read-only, side-effect free]. Simulates statutory tax credits under Piano Transizione 5.0 (Art. 38 D.L. 19/2024 & D.M. 24/07/2024) across 3 investment brackets and certified energy reduction tiers (3-15%), including high-efficiency solar PV bonuses (+12%/+14%) and eligible training expenses. Usage: Use this tool to model corporate tax credits for energy-efficient capital goods investments under PNRR Mission 7. Returns: JSON object with { companyName: string, isEligible: boolean, reductionTierAchieved: string, baseTaxCreditRatePercent: number, breakdown: object, effectiveBlendedSubsidyIntensityPercent: number, compensationRules: object }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companyName": "<companyName>",
      "totalInvestmentCapitalGoods40Eur": "<totalInvestmentCapitalGoods40Eur>",
      "reductionScope": "<reductionScope>",
      "certifiedEnergyReductionPercent": "<certifiedEnergyReductionPercent>",
      "dnshCriteriaMet": "<dnshCriteriaMet>"
    },
    "name": "transizione5_incentive_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNameYesInvesting enterprise corporate name
pvModuleClassNoENEA register efficiency class for solar modules (D.L. 181/2023)
reductionScopeYesEnergy savings perimeter: enterprise structure (min 3%) or production process (min 5%)
dnshCriteriaMetYesWhether investment strictly complies with Do No Significant Harm (DNSH) environmental principles
trainingCostsEurNoWorkforce training expenditure in green/digital skills (capped at 10% of investment up to €300k)
photovoltaicInvestmentEurNoOptional investment in self-generation renewable solar PV assets in EUR
certifiedEnergyReductionPercentYesEnergy consumption reduction percentage certified by an ENEA-accredited auditor
totalInvestmentCapitalGoods40EurYesEligible investment in Industry 4.0 capital goods (Annex A & B) in EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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; the description reinforces this with 'Deterministic calculation, read-only, side-effect free', which adds the useful determinism guarantee. It does not disclose how ineligible or DNSH-failing inputs are handled, whether any assumption/validation errors are raised, or any statutory limits on when the calculation is admissible.

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 front-loaded and cleanly organised into declaration, Usage, and Returns sections. Minor redundancy exists — 'read-only, side-effect free' restates the annotations and the bracket/tier enumeration is compressed to the point of being decorative rather than operative.

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?

For an 8-parameter, 5-required calculator with no output schema, the description supplies an explicit return-object shape (isEligible, reductionTierAchieved, breakdown, effectiveBlendedSubsidyIntensityPercent), which is the key missing piece an agent would otherwise lack. It stops short of explaining eligibility gating semantics (DNSH, minimum reduction thresholds) or edge-case behaviour.

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% with two documented enums, so the schema already carries the parameter meaning and a baseline 3 applies. The description adds regulatory framing (brackets, PV efficiency bonuses +12%/+14%, ENEA-certified reduction tiers) but does not map any of that detail onto specific parameters beyond what the schema 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 names a specific verb and resource ('Simulates statutory tax credits under Piano Transizione 5.0'), pins the legal basis (Art. 38 D.L. 19/2024 & D.M. 24/07/2024), and scopes the domain (3 investment brackets, 3-15% energy reduction tiers, PV bonuses, training costs). It is clearly distinguishable from generic sibling calculators such as dcf_wacc_valuation or bando_thresholds_calculator.

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 'Usage:' sentence gives a clear triggering condition — model corporate tax credits for energy-efficient capital goods investments under PNRR Mission 7. It does not, however, state when NOT to use it or point to neighbouring incentive calculators (e.g., cer_incentivi_gse_calculator, de_minimis_state_aid_screener) that could plausibly be confused with it.

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