Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_estimate_cbam_liability

Read-onlyIdempotent

Calculate EU CBAM liability by CN code and origin country, including embedded emissions, free allocation phase-out deductions, and net certificate cost in EUR.

Instructions

Calculate EU CBAM (Regulation 2023/956) embedded direct/indirect/precursor emissions by CN code, 2026-2034 free allocation phase-out deduction, and net payable CBAM certificate cost in EUR.

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": {
      "cnCode": "<cnCode>",
      "originCountry": "<originCountry>"
    },
    "name": "climeq_estimate_cbam_liability"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnCodeYesEU Combined Nomenclature code (e.g., '7208' steel, '7601' aluminum, '2523' cement).
netMassTonsNo
originCountryYesISO country of origin (e.g., 'TR', 'IN', 'CN').
reportingYearNo
productDescriptionNo
precursorEmissionsTco2eNo
euEtsCarbonPriceEurPerTonNo
directEmissionsTco2ePerTonNo
electricityConsumptionMwhPerTonNo
carbonPricePaidInOriginEurPerTonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered; the description adds that the result is a phased free-allocation deduction and a net EUR certificate cost. It does not disclose what happens when the many optional inputs (direct emissions, electricity, precursor emissions) are omitted, whether defaults represent real values or fallbacks, or how the 2026-2034 phase-out factors are derived - a meaningful gap for an estimation tool with 8 optional parameters.

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 densely packed sentence with no filler; the calculation target, the phase-out window and the output currency are all front-loaded. It is slightly over-compressed - three distinct outputs are chained together - but nothing is wasted.

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?

For a 10-parameter estimation tool with no output schema and low schema description coverage, the description should explain input fallbacks and what the returned figures include. It covers the calculation's components well but leaves the agent guessing about default handling and result structure before calling.

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 20% across 10 parameters, so the description must carry more weight. It conceptually maps several inputs ('by CN code', direct/indirect/precursor emissions, 2026-2034 reporting year, EUR certificate cost) but gives no per-parameter meaning, units alignment, or interaction rules for euEtsCarbonPriceEurPerTon, carbonPricePaidInOriginEurPerTon or the intensity inputs.

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?

The description names a specific verb ('Calculate') and a precise resource ('EU CBAM ... embedded direct/indirect/precursor emissions ... net payable CBAM certificate cost in EUR'), and anchors it to Regulation 2023/956. No sibling tool (PCF, freight, electricity, fuel calculators) does CBAM certificate liability, so an agent can distinguish it without opening any schema.

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: the mention of CN codes, origin country and 2026-2034 phase-out suggests CBAM-reportable goods imported into the EU, but the description never states when to pick this over climeq_calculate_pcf or climeq_estimate_by_classification, nor any prerequisite such as scope coverage or reporting-year constraints.

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