Skip to main content
Glama

case_green_epbd_target_audit

Read-onlyIdempotent

[Deterministic building energy decarbonization audit. Pure calculation, read-only, side-effect free]. Computes mandatory 2030 (-16%) and 2035 (-21%) primary energy cut targets under EPBD IV Directive (EU) 2024/1275 ('Case Green'), audits worst-performing 43% building stock, and flags statutory 2025 fossil boiler subsidy prohibitions. Usage: Use this tool to evaluate real estate energy performance, mandatory renovation trajectories, and heating decarbonization under EPBD IV. Returns: JSON object with { isWorstPerformingBuildingStock: boolean, baselineAnnualPrimaryEnergyKwh: number, epbd2030Target: object, epbd2035Target: object, heatingSystemCompliance: object, renovationRoadmap: array }.

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": {
      "buildingType": "<buildingType>",
      "currentEnergyClass": "<currentEnergyClass>",
      "epglNren_kWh_m2_year": "<epglNren_kWh_m2_year>",
      "floorAreaM2": "<floorAreaM2>",
      "heatingSystem": "<heatingSystem>"
    },
    "name": "case_green_epbd_target_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
floorAreaM2YesUseful heated floor area in square meters
buildingTypeYesBuilding functional typology
heatingSystemYesPrimary space heating generator
constructionYearNoOriginal construction year
currentEnergyClassYesCurrent APE energy class
hasSolarPvInstalledNoWhether rooftop solar PV is already operating
epglNren_kWh_m2_yearYesEPgl,nren non-renewable primary energy index from APE certificate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint; the description reinforces this with 'pure calculation, side-effect free' and adds 'deterministic', which tells the agent identical inputs always yield identical results. It also enumerates the return object keys, which is valuable given no output schema exists. Minor overlap with the annotations prevents a 5.

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?

Structure is strong: a bracketed tagline stating determinism and safety, then explicit 'Usage' and 'Returns' segments, all front-loaded. It is dense for three sentences but every clause carries regulatory or output information; the only waste is restating read-only behavior already in the annotations.

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, five required, no output schema, and domain-specific EPBD/APE terminology, the definition does what matters: it names the target percentages and lists every returned field. An agent could invoke it without further reading, though it does not explain how renovationRoadmap or heatingSystemCompliance are derived.

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 enums on buildingType, currentEnergyClass, and heatingSystem, so the schema already carries the parameter burden and baseline 3 applies. The description adds conceptual grounding by referencing the EPgl,nren primary energy index and heating system compliance, but no format, unit, or edge-case guidance beyond the schema.

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 precise verb-and-resource set: computing EPBD IV 2030 (-16%) and 2035 (-21%) primary energy targets, auditing the worst-performing 43% of stock, and flagging 2025 fossil boiler subsidy prohibitions. The regulatory citation (EU) 2024/1275 and the concrete percentages make it unmistakable which calculation this tool performs, and it is clearly distinct from the billing, incentive, and carbon-tax 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?

The 'Usage' sentence gives clear context: evaluate real estate energy performance, mandatory renovation trajectories, and heating decarbonization under EPBD IV. It does not name exclusion conditions or point to any alternative tool for adjacent questions, so it stops short of the when/when-not threshold, but the intended call context is unambiguous.

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