engineering

digital_renovation_passport

EPBD-style staged digital renovation passport: 3-phase roadmap (quick wins, system upgrades, deep renovation) with cost ranges, energy savings and EPC trajectory from current EPC, floor area and heating type. Indicative.

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": {
      "floor_area_m2": "<floor_area_m2>",
      "current_epc": "<current_epc>",
      "heating": "<heating>"
    },
    "name": "digital_renovation_passport"
  }
}

Input Schema

Name	Required	Description
`era`	No	Construction era (label only)
`address`	No	Building address (label only)
`country`	No	Country code (e.g. UK, DE)
`heating`	Yes	Primary heating system
`current_epc`	Yes	Current EPC band A-G
`building_type`	No	Building type (label only)
`floor_area_m2`	Yes	Gross floor area (m2)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the disclosure burden. It adds meaningful context by calling the result 'Indicative' and by specifying the output dimensions. However, it does not disclose assumptions, data sources, accuracy limits, or the exact return format.

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?

The description is compact: one substantive sentence followed by the single caveat 'Indicative.' It front-loads the core behavior and output without repeating schema field descriptions or adding filler.

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 a non-destructive estimation tool, this is sufficient: it states the analytic inputs, the high-level output structure, and the indicative nature, while the schema documents all parameters. It would benefit from explicit units or a return-value shape, but nothing essential for selecting or invoking the tool is missing.

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 100%, so the baseline is 3. The description adds value by explicitly naming current EPC, floor area, and heating type as the drivers of the roadmap, implying that other fields are contextual labels rather than calculation inputs.

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 clearly identifies the deliverable—a 3-phase renovation roadmap with cost ranges, energy savings, and EPC trajectory—and the EPBD framing helps distinguish it from the sibling tools. It lacks an explicit action verb like 'generates' or 'calculates', but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The EPBD-style, staged-renovation framing and the word 'Indicative' imply the intended scenario of rough renovation planning, but the agent must infer this from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All engineering tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?