engineering

calculate_carbon

Calculate operational + embodied carbon and net-zero gap (CIBSE TM65 / RICS WLCA). Returns carbon intensity, benchmark, and prioritised reduction measures with payback.

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>",
      "building_type": "<building_type>",
      "country": "<country>"
    },
    "name": "calculate_carbon"
  }
}

Input Schema

Name	Required	Description
`country`	Yes	ISO-2: gb, de, fr, nl, es, pl, ro, it, ae, us
`building_type`	Yes	office, residential, retail, industrial, hospital, warehouse, hotel
`floor_area_m2`	Yes
`energy_kwh_year`	No	Measured annual energy; 0 to use benchmark
`construction_year`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 26, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the outputs (carbon intensity, benchmark, prioritised reduction measures with payback), but it omits assumptions, default behavior for missing optional parameters, and any limitations or data requirements.

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?

A single sentence that front-loads the core purpose, then lists the return outputs without waste. The standard references add useful precision without bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description states what the tool returns, which is useful given there is no output schema, but it omits required parameter semantics, default behaviors, and sibling differentiation. For a five-parameter calculator with no annotations, this is minimally adequate but leaves meaningful gaps.

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

Parameters2/5

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

Schema description coverage is only 60%, leaving floor_area_m2 and construction_year undocumented. The description does not compensate by explaining parameter meaning, units, or defaults such as using benchmark values when energy_kwh_year is absent. It adds little semantic value beyond the schema.

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 names a specific verb and resource: calculating operational and embodied carbon plus the net-zero gap, and cites CIBSE TM65 / RICS WLCA. This is clear and specific, though it does not explicitly differentiate itself from siblings like building_carbon_footprint or eu_cost_benchmarking.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool over related carbon or benchmarking tools. It neither states typical use cases nor names alternatives, so an agent must infer selection context from the sibling list alone.

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?