Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_fuel

Calculate Scope 1 direct combustion (TTW), biofuel blend (B5-B100, E5-E100, HVO100, SAF), hydrogen, biogenic CO2, and Scope 3.3 WTT emissions from fuel type and amount.

Instructions

Calculate Scope 1 direct combustion (TTW), biofuel blends (B5-B100, E5-E100, HVO100, SAF), hydrogen conversions, out-of-scope biogenic CO2, and Scope 3.3 upstream WTT.

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

Input Schema

NameRequiredDescriptionDefault
unitNoL
amountYes
regionNo
persistNo
fuelTypeYese.g., 'diesel', 'diesel_b7', 'hvo100', 'natural_gas', 'saf', 'hydrogen'.

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 openWorldHint=true and non-idempotent, but do not explain the readOnlyHint=false pairing with a 'persist' flag defaulting to false, and the description says nothing about whether anything is written or which factor sources/regions get resolved. It does add genuine behavioral context by drawing scope boundaries (TTW vs WTT, biogenic CO2 treated as out-of-scope), which is value beyond the annotations.

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 dense sentence with no filler, and it front-loads the primary scope (Scope 1 TTW) before the secondary scopes. It is efficient, though the comma-list runs on and provides no visual structure for scanability.

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?

This is wrong to score high — the tool has 5 parameters, 20% schema coverage, no output schema, and a persist/readOnly mismatch the description never resolves. For an open-world calculation tool whose results depend on region and unit, the description leaves too much for the agent to guess.

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 20% (just fuelType), so the description needs to compensate for unit, amount, region, and persist. It partly helps on fuelType by naming blends and fuel codes, but region (which drives factor selection for an open-world tool), unit, and especially persist are left entirely unexplained by both schema and description.

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 opens with a specific verb (Calculate) and enumerates exactly what it covers: Scope 1 direct combustion TTW, biofuel blends with named blend ranges and fuel codes, hydrogen, biogenic CO2, and Scope 3.3 WTT. That is far more specific than the bare name, though it never states how it differs from fuel-adjacent siblings such as climeq_calculate_electricity or climeq_calculate_heat_steam.

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?

Scope wording ('Scope 1 direct combustion', 'Scope 3.3 upstream WTT') implicitly tells the agent this is the tool for liquid/gaseous fuel combustion, and enumerating fuel families signals valid inputs. There is, however, no explicit when-to-use / when-not-to-use statement and no pointer to an alternative for electricity, heat/steam, or travel emissions.

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