Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_heat_steam

Calculate Scope 2 emissions from purchased district heating, steam, hot water, or cooling, including distribution thermal losses and Scope 3.3 FERA for accurate energy accounting.

Instructions

Calculate Scope 2 purchased district heating, steam, hot water, or cooling emissions plus distribution thermal losses and Scope 3.3 FERA.

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": {
      "amount": "<amount>"
    },
    "name": "climeq_calculate_heat_steam"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoMWh
amountYes
regionNoGlobal
persistNo
energyTypeNodistrict_heating
thermalLossPercentNo
includeWttAndThermalLossesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior3/5

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

The description adds real scope behavior beyond the annotations by stating that distribution thermal losses and Scope 3.3 FERA are included in the result. However, it omits the most important behavioral trait for this tool: annotations declare readOnlyHint=false and idempotentHint=false, and a `persist` flag exists, yet the description never says that a calculation can write a record or that repeated calls may create duplicates.

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?

A single front-loaded sentence with no filler, and the primary scope (Scope 2 purchased heat) leads before the secondary add-ons. Slight deduction for cramming three concepts into one clause and using the unexplained abbreviation "FERA".

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

Completeness2/5

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

This is a multi-parameter emissions calculator with no output schema and no annotation coverage of return behavior, so the description should explain what the calculation yields (emissions figure, breakdown by scope, factor used). It also leaves the persistence side effect and thermal-loss percentage semantics unexplained, which is not enough for a tool of this complexity.

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 0% across 7 parameters, so the description must compensate and largely does not. It implicitly covers `energyType` (the five accepted carriers) and the idea of an `amount`, but `unit`, `region`, `thermalLossPercent`, `persist`, and `includeWttAndThermalLosses` receive no explanation of meaning, valid ranges, defaults, or effect on the output.

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?

Uses a specific verb ("Calculate") with a precisely scoped resource: Scope 2 purchased district heating, steam, hot water, or cooling emissions, plus thermal losses and Scope 3.3 FERA. The energy-carrier enumeration clearly separates it from siblings such as calculate_electricity or calculate_fuel, though it never names an alternative explicitly.

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?

Usage is only implied by the resource scope: an agent can infer this is the tool for purchased heat/steam/cooling rather than electricity or fuels. There is no explicit when-to-use vs. when-not guidance, no mention of prerequisites (region data availability, factor sources), and no routing to siblings.

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