Skip to main content
Glama

ets2_carbon_tax_projector

Read-onlyIdempotent

[Deterministic building & transport carbon tax projection. Pure calculation, read-only, side-effect free]. Calculates the financial impact of the EU ETS 2 carbon pricing system starting 2027 under Directive (EU) 2023/959 for natural gas, heating oil, and LPG across base ceiling (€45), market (€65), and stress (€90) EUA-2 price scenarios. Usage: Use this tool to forecast carbon tax surcharges on fossil fuels and evaluate heat pump ROI. Returns: JSON object with { totalAnnualEmissionsTco2e: number, unitCarbonTaxSurchargeEur: object, totalAnnualCarbonTaxCostEur: object, tenYearCumulativeCarbonCostEur: object, decarbonizationEconomics: 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": {
      "fuelType": "<fuelType>",
      "annualConsumptionUnits": "<annualConsumptionUnits>"
    },
    "name": "ets2_carbon_tax_projector"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelTypeYesFossil heating fuel
projectionYearNoTarget forecast year (2027-2030)
annualConsumptionUnitsYesAnnual consumption in Smc or Liters
customEuaCarbonPriceEurPerTonNoOptional custom EUA-2 allowance price in EUR/tCO2e

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'pure calculation, read-only, side-effect free' plus determinism. It adds genuinely new behavioral context the annotations do not: the three price scenarios (€45/€65/€90) and the years the model spans. It does not say how projectionYear or a custom EUA price interacts with the built-in scenarios, which leaves a minor gap.

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?

Three compact sentences: purpose and constraints first, usage second, return shape third. Every clause carries information (fuels, directive, scenarios, output keys) with no filler or repetition.

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?

There is no output schema, and the description compensates by enumerating the top-level return keys, which is the main thing an agent needs. It omits default behavior for the optional projectionYear and custom price parameters and the internal structure of the returned per-scenario objects, a small residual gap for a four-parameter calculation tool.

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 baseline is 3. The description adds some meaning beyond the schema by naming the three price scenarios that presumably underlie customEuaCarbonPriceEurPerTon, but it never states defaults, the default projection year, or how a custom price overrides the scenario set, so the added value is modest.

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 financial impact of the EU ETS 2 carbon pricing system'), the fuels covered, the start year, and the regulatory basis (Directive (EU) 2023/959). An agent knows exactly what computation this performs without opening the schema, and the fuel/price-scenario scope distinguishes it from the accounting-style siblings.

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?

'Use this tool to forecast carbon tax surcharges on fossil fuels and evaluate heat pump ROI' gives a clear context of use. It stops short of explicit exclusions or naming an alternative tool for adjacent questions (e.g. incentive calculations, which siblings appear to cover), so it is clear but not complete guidance.

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