Skip to main content
Glama

NovaPixel LexGrid

cbam_embedded_emissions

Calculates direct and indirect embedded emissions (tCO2e) and projected EU ETS CBAM certificate liability under Regulation (EU) 2023/956.

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
goodCategoryYes
quantityMetricTonsYesImported quantity in metric tons
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
indirectEmissionsPerTon_tCO2eNoSpecific indirect electricity emission factor
carbonPriceAlreadyPaidInOriginEurPerTonNoCarbon tax already paid in country of origin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It usefully discloses that both direct and indirect emissions are covered and that the second output is a projected certificate liability, but it says nothing about how missing optional emission factors are handled (regulatory defaults?), whether the carbon-price-paid input is deducted, or that the tool is a pure computation with no side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb, states the units of the primary output, and identifies the legal basis. Nothing is redundant and nothing is padded.

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 7-parameter regulatory calculator with no annotations and no output schema, the definition is minimally adequate: it names the outputs conceptually. It falls short on how the optional factor parameters and the ETS price default (70 EUR/tCO2e, visible only in the schema) affect the result, which matters for an agent deciding what to supply.

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 86%, so the schema already documents the parameters, including the ISO code and quantity units. The description adds no parameter-level meaning beyond that — notably it does not explain whether directEmissionsPerTon_tCO2e and indirectEmissionsPerTon_tCO2e are optional inputs with regulatory default fallbacks.

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?

It opens with a specific verb ("Calculates") tied to a precisely named resource set: direct and indirect embedded emissions in tCO2e plus projected CBAM certificate liability, anchored to Regulation (EU) 2023/956. The scope is unambiguous, though it offers no explicit contrast to the sibling tools (dual_use_export_control, incoterms_cost_allocator, taric_hs_validator), which are in different domains anyway.

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 when-to-use or when-not-to-use guidance, no statement of a precondition (e.g. that a good must fall in an EU CBAM scope category), and no mention of alternatives for adjacent tasks. An agent must infer from the name and the regulation citation alone that this is the CBAM computation path.

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