Skip to main content
Glama

cbam_embedded_emissions

Read-onlyIdempotent

[Deterministic customs carbon calculation. Pure calculation, read-only, side-effect free]. Calculates direct and indirect embedded greenhouse gas emissions (tCO2e) and projected EU ETS CBAM certificate purchase liabilities under Regulation (EU) 2023/956 across iron/steel, aluminium, cement, fertilizers, hydrogen, and electricity imports, factoring in carbon taxes already paid in country of origin. Usage: Use this tool to calculate import carbon tariff exposure under EU CBAM rules. For enterprise Scope 1 & 2 carbon accounting, use 'csrd_esg_calculator' instead. Returns: JSON object with { goodCategory: string, quantityMetricTons: number, totalEmbeddedEmissions_tCO2e: number, grossCbamLiabilityEur: number, netCbamLiabilityEur: number, etsPriceUsedEur: number }.

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": {
      "goodCategory": "<goodCategory>",
      "quantityMetricTons": "<quantityMetricTons>",
      "countryOfOriginIso2": "<countryOfOriginIso2>"
    },
    "name": "cbam_embedded_emissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
goodCategoryYesCBAM Annex I aggregate goods category
quantityMetricTonsYesImported quantity in metric tons (net mass)
countryOfOriginIso2Yes2-letter ISO country code of origin (e.g. CN, IN, TR)
estimatedEtsPriceEurPerTonNoProjected EU ETS certificate price (default 70€/tCO2e)
directEmissionsPerTon_tCO2eNoSpecific direct emission factor in tCO2e/t (default EU benchmark used if omitted)
indirectEmissionsPerTon_tCO2eNoSpecific indirect electricity emission factor in tCO2e/t
carbonPriceAlreadyPaidInOriginEurPerTonNoVerified carbon tax or ETS price already paid in country of origin in EUR/t

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / carbonPriceAlreadyPaidInOriginEurPerTon / description
      Previous value: -"Carbon tax already paid in country of origin"New value: +"Verified carbon tax or ETS price already paid in country of origin in EUR/t"
    • changedInput schema / properties / directEmissionsPerTon_tCO2e / description
      Previous value: -"Specific direct emission factor in tCO2e/t"New value: +"Specific direct emission factor in tCO2e/t (default EU benchmark used if omitted)"
    • addedInput schema / properties / estimatedEtsPriceEurPerTon / default
      Added value: +70
    • addedInput schema / properties / goodCategory / description
      Added value: +"CBAM Annex I aggregate goods category"
    • changedInput schema / properties / indirectEmissionsPerTon_tCO2e / description
      Previous value: -"Specific indirect electricity emission factor"New value: +"Specific indirect electricity emission factor in tCO2e/t"
    • changedInput schema / properties / quantityMetricTons / description
      Previous value: -"Imported quantity in metric tons"New value: +"Imported quantity in metric tons (net mass)"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description reinforces this with 'pure calculation, side-effect free' and adds genuinely new context: the regulatory basis (Regulation EU 2023/956), the goods scope, and that carbon taxes paid in the origin country are netted out. It stops short of explaining edge behavior such as how missing emission factors are handled, which the schema mentions but the description does not.

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?

Front-loaded with the core purpose, then usage, then return shape, which is an effective order for an agent. Minor waste in the bracketed '[Pure calculation, read-only, side-effect free]' tag, which largely restates the supplied annotations.

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

Completeness5/5

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

For a seven-parameter calculation tool with no output schema, the description supplies the missing piece: an explicit enumeration of the returned JSON fields. Combined with the fully documented input schema and the named alternative tool, an agent has everything needed to select and invoke it correctly.

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 100%, so the schema already documents all seven parameters, including the EU benchmark default for omitted emission factors and the 70€ default ETS price. The description adds only the conceptual note that origin-country carbon taxes are factored in, which maps to one parameter; baseline 3 applies.

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?

States a specific verb and resource: calculates direct and indirect embedded GHG emissions (tCO2e) and projected EU ETS CBAM certificate liabilities for named goods categories under a named regulation. It also explicitly separates itself from the sibling 'csrd_esg_calculator' by contrasting import carbon tariff exposure with enterprise Scope 1 & 2 accounting.

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

Usage Guidelines5/5

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

Provides an explicit 'Usage' line stating when to use it and names the alternative tool plus the condition that selects that alternative (enterprise Scope 1 & 2 accounting). No inference is required to route between the two.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources