Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_electricity

Calculates GHG Protocol Scope 2 location-based and market-based electricity emissions plus Scope 3 FERA (WTT and T&D losses) from kWh amount, grid zone, and certificates.

Instructions

Calculate GHG Protocol Scope 2 dual reporting (Location-Based + AIB Residual Mix Market-Based with GO/IREC/YEK-G/PPA certificates) and Scope 3 Category 3 FERA (WTT + T&D losses).

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>",
      "countryOrGridZone": "<countryOrGridZone>"
    },
    "name": "climeq_calculate_electricity"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNokWh
yearNo
amountYes
persistNo
contractTypeNo
certificateIdNo
includeWttAndTdNo
countryOrGridZoneYesCountry or sub-grid code (e.g., 'TR', 'DE', 'FR').
greenElectricityKwhNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-idempotent, network-touching operation. The description adds useful domain framing (which reporting standards and certificate schemes apply) but says nothing about the persist side effect, which emission-factor sources are queried, or why the call is not read-only. A partial credit of 3 fits: some added context, meaningful behavioral gaps.

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?

One dense sentence with the core reporting scope front-loaded and no filler. It is jargon-heavy but every clause carries scope information; only the parenthetical certificate list is arguably over-packed for its length.

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?

For a 9-parameter, non-idempotent, network-calling calculator with no output schema, the definition leaves too much unexplained: how location-based versus market-based results are selected, what persist does, and what the inputs like greenElectricityKwh or certificateId change. The methodology naming is good, but an agent could not call this correctly without guessing at most parameters.

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 only 11% across 9 parameters, so the description needs to compensate. It does map partially onto contractType by naming GO/IREC/YEK-G/PPA certificates, but amount, unit, year, persist, certificateId, includeWttAndTd, countryOrGridZone and greenElectricityKwh are left entirely to the bare schema. The single enum mention is real added meaning, so it is above the minimum, but far short of full coverage.

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?

Uses a specific verb ('Calculate') with a precisely scoped resource: GHG Protocol Scope 2 dual reporting (location-based + AIB residual mix market-based) plus Scope 3 Cat 3 FERA/WTT/T&D. The electricity domain, together with the named methodologies, clearly separates it from sibling calculators like climeq_calculate_air_travel or climeq_calculate_heat_steam without needing to name them.

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?

There is no guidance on when to use this versus alternatives (e.g., heat/steam or fuel calculators) and no prerequisites stated, such as requiring contractType for a market-based result. The domain wording implies purchased-electricity use cases, but nothing is explicit and no exclusions are given.

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