Skip to main content
Glama

arera_bill_decomposer

Read-onlyIdempotent

[Deterministic Italian electric & gas bill decomposition. Pure calculation, read-only, side-effect free]. Algorithmic breakdown of electricity and natural gas bills under ARERA regulatory texts (TIT/TIF), separating energy raw commodity (PUN/PSV), commercialization PCV, network transport and meter management, general system charges (ASOS/ARIM), and excise/VAT taxes. Usage: Use this tool to audit corporate and domestic utility invoices, verify regulated tariff components, and check energy-intensive exemptions. Returns: JSON object with { costDecompositionEur: object, unitCostAverages: object, costSharePercentages: object, auditVerdict: 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": {
      "utilityType": "<utilityType>",
      "customerType": "<customerType>",
      "billedUnits": "<billedUnits>",
      "billingPeriodDays": "<billingPeriodDays>"
    },
    "name": "arera_bill_decomposer"
  }
}

Input Schema

NameRequiredDescriptionDefault
billedUnitsYesBilled consumption volume (kWh or Smc)
utilityTypeYesCommodity type
customerTypeYesCustomer contract category
billingPeriodDaysYesBilling interval in days (e.g. 30 or 61)
contractedPowerKwNoContracted power in kW (for electricity, e.g. 3, 15, 30)
energyRawPriceEurPerUnitNoSpecific energy wholesale or contracted rate in EUR/unit
isEnergyIntensiveCompanyNoWhether enterprise is registered as energy-intensive (energivoro) for ASOS discount

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds that the tool is deterministic and a pure calculation with no side effects, plus a 'Returns' block listing the four output keys. It does not cover preconditions such as which inputs are mandatory per utility type or how missing optional rates are defaulted.

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 definition is front-loaded with a bracketed role statement, then Usage and Returns sections, so scanning is easy. The bracket text ('Pure calculation, read-only, side-effect free') partially duplicates the deterministic/read-only claims and the annotations, which is minor waste.

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 seven parameters and no output schema, the definition compensates by enumerating the returned JSON keys and the regulatory components covered. It leaves some gaps on conditional parameters (e.g. contractedPowerKw only applies to ELECTRICITY) and implicit EUR currency, but nothing blocking for a correct call.

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 the schema already documents all seven parameters including units and enums; this sets the baseline at 3. The description does add domain meaning by tying 'energy raw commodity' to PUN/PSV and naming ASOS/ARIM, but it never maps parameters to those concepts explicitly.

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 states a specific verb+resource ('Algorithmic breakdown of electricity and natural gas bills') and scopes it to ARERA TIT/TIF regulatory components, so an agent knows exactly what is computed. No sibling tool is named, but the domain (bill decomposition vs. EPBD audit, GSE incentives, ETS2 projection) is narrow enough to be self-distinguishing.

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 concrete call contexts: auditing corporate and domestic utility invoices, verifying regulated tariff components, and checking energy-intensive exemptions. It stops short of stating when NOT to use it or naming an alternative tool for hypothetical non-ARERA bill checks.

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