Skip to main content
Glama

eu_carbon_customs

Retrieves EU CBAM default embedded emissions by CN/TARIC code and origin country, with optional shipment mass and certificate cost inputs to estimate emissions and CBAM costs.

Instructions

EU CBAM (carbon border adjustment) default embedded emissions for a CN/TARIC code and country of origin, from the official Commission default-values file: direct, indirect and total tCO2e per tonne, production route, year mark-up, and optional embedded emissions and certificate cost for a shipment (tonnes, EUR price). Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "cn": "<cn>",
      "country": "<country>"
    },
    "name": "eu_carbon_customs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnYesCN/TARIC code 4-10 digits
yearNo2026+
tonnesNoShipment mass in tonnes (optional)
countryYesOrigin country name or ISO alpha-2
price_eurNoCBAM certificate price EUR/tCO2e (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the per-call price (0.003 USDC on Base), the x402 payment mechanism, and the exact failure mode when no payment key is present (a 402 challenge, not an error). It also discloses data provenance. It does not describe behavior for invalid/unknown CN codes or rate limits, which keeps it below a 5.

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?

The core identity is front-loaded in the first clause and no sentence is filler. It is dense—one long compound sentence carrying data source, outputs, shipment extension, pricing, and payment failure—which costs some scannability but wastes nothing.

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?

There is no output schema, and the description compensates by enumerating the returned fields (direct, indirect, total tCO2e per tonne, production route, year mark-up), plus cost and auth behavior. What is missing is error semantics for unrecognized CN/TARIC codes or unsupported origin countries, which matters for a 5-parameter lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning: 'year mark-up' explains what the year parameter affects, and 'for a shipment (tonnes, EUR price)' clarifies that tonnes and price_eur are jointly used to derive embedded emissions and certificate cost. That linkage is not obvious from the schema alone.

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?

Names the specific artifact (EU CBAM default embedded emissions), the exact lookup keys (CN/TARIC code and country of origin), the data source (official Commission default-values file), and enumerates the returned measures (direct, indirect, total tCO2e/tonne, production route, year mark-up). No sibling in the supplied list touches carbon border data, so an agent can identify the right tool immediately.

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

Usage Guidelines4/5

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

Gives clear context for use: look up CBAM defaults for a CN code plus origin, and optionally extend to a shipment by supplying tonnes and a EUR certificate price. It also states the practical precondition for calling at all (payment key required, otherwise a 402 is returned). It stops short of explicit when-not guidance or named alternatives, so it is a 4 rather than a 5.

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