Skip to main content
Glama

cer_incentivi_gse_calculator

Read-onlyIdempotent

[Deterministic Renewable Energy Communities incentive calculator. Pure calculation, read-only, side-effect free]. Calculates the 20-year GSE incentive tariff premium for CERs under D.M. MASE 414/2023 and ARERA TIAD 727/2022/R/eel, applying capacity tiers (<=200kW, 200-600kW, >600kW), geographic insolation corrections (Nord/Centro/Sud), and PNRR 40% capital grant adjustments. Usage: Use this tool to model financial returns for renewable energy communities, self-consumption groups, and solar cooperatives. Returns: JSON object with { plantPowerTier: string, tariffBreakdownEurPerMwh: object, economicRevenue: object, pnrrGrantStatus: 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": {
      "plantNominalPowerKw": "<plantNominalPowerKw>",
      "geographicZone": "<geographicZone>",
      "annualProductionMWh": "<annualProductionMWh>",
      "annualSharedEnergyMWh": "<annualSharedEnergyMWh>"
    },
    "name": "cer_incentivi_gse_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
geographicZoneYesItalian geographic macro-zone for insolation correction
annualProductionMWhYesTotal annual electricity generated by the plant in MWh
plantNominalPowerKwYesRenewable plant peak power in kW (up to 1,000 kW)
annualSharedEnergyMWhYesAnnual energy shared under the primary electrical substation in MWh
referencePunEurPerMwhNoReference PUN wholesale electricity price (default €110/MWh)
pnrrCapitalGrant40PercentAppliedNoTrue if the project benefits from PNRR 40% non-repayable capital grant (<5k inhabitants)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds genuinely new behavioral context: the calculation is described as deterministic, pure, and side-effect free, which tells the agent repeated calls yield identical values with no external state change. It also discloses the regulatory basis and the 20-year horizon, which annotations cannot convey. It stops short of describing validation failures or out-of-range handling.

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 front-loaded — a bracketed behavioral tag, then the calculation specification, then explicit 'Usage' and 'Returns' sections. There is slight redundancy between the bracketed 'Pure calculation, read-only, side-effect free' and the existing readOnlyHint annotation, but no sentence is wasted.

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 six parameters, no output schema, and financial stakes, the description carries the right load: it supplies an explicit return shape ({ plantPowerTier, tariffBreakdownEurPerMwh, economicRevenue, pnrrGrantStatus }) that the missing output schema would otherwise leave unknown, plus the regulatory framing. Small gaps remain around input validation rules and the €1,000 kW upper bound's consequences.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real interpretive meaning: the capacity thresholds (<=200kW, 200-600kW, >600kW) explain how plantNominalPowerKw drives the tariff tier, and the Nord/Centro/Sud insolation correction explains geographicZone's effect. Minor imprecision: the description says 'Sud' while the schema enum value is 'SUD_ISOLE'.

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 20-year GSE incentive tariff premium for CERs' — and grounds it in named regulations (D.M. MASE 414/2023, ARERA TIAD 727/2022/R/eel) plus the exact calculation components (capacity tiers, geographic insolation correction, PNRR grant adjustment). This is far more specific than the sibling tools' domains and lets an agent distinguish it without opening the schema.

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' line gives a clear positive trigger: modeling financial returns for renewable energy communities, self-consumption groups, and solar cooperatives. However, it offers no exclusions or routing guidance against the adjacent energy-economics siblings (e.g. arera_bill_decomposer, ets2_carbon_tax_projector), so an agent must infer when this is not the right choice.

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