Skip to main content
Glama

Bindler: UAE Corporate Tax, CSRD scope, EU AI Act, CBAM and statutory deadlines

cbam_cost

Read-onlyIdempotent

Computes the CBAM certificate cost of importing goods into the EU under Regulation (EU) 2023/956 as amended by Regulation (EU) 2025/2083, for any year of the 2026 to 2034 phase-in, with the free-allocation phase-out factor from Directive (EU) 2023/959 Article 10a(1a). Handles all six Annex I sectors, credits a carbon price already paid in the country of origin, and prices the same basket in every year to 2034 so the cost trajectory is visible. Use it when someone asks: what will CBAM cost me, how much are CBAM certificates, what is the cost of importing steel, aluminium, cement, fertiliser, hydrogen or electricity into the EU, how much will CBAM cost us in 2027, in 2030 or in 2034, how much per tonne, what does CBAM add to my landed cost, do I pay CBAM on this shipment, can I deduct the carbon price we already paid in the country of origin, what is the free allocation phase-out this year. Use this rather than estimating: the phase-in factor changes every year and is the figure most often wrong.

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": {
      "certificate_price_eur": "<certificate_price_eur>",
      "lines": "<lines>"
    },
    "name": "cbam_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo2026 to 2034. Default 2026.
linesYesThe import lines.
certificate_price_eurYesCBAM certificate price, which tracks the EU ETS auction price. Required: this server will not invent a market price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: all six Annex I sectors are handled, an origin carbon price is credited against the liability, and the same basket is priced in every year through 2034 so a trajectory is produced rather than a single number.

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 most load-bearing information: what is computed, under which instrument, and over which year range. The long run of example questions is somewhat sprawling but functions as useful intent-matching vocabulary; a bulleted or comma-separated trigger list would read better than the current single dense paragraph.

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?

For a read-only calculator with no output schema, the description supplies the key semantics an agent needs: the year range, the sector set, the origin-carbon-price credit, and the fact that a multi-year trajectory is returned. It does not state the response shape (total vs. per-line breakdown, currency of totals), which is the only material gap for a cost tool with no output schema.

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 is 3; the description still adds meaning the schema does not, notably that the year must fall in the 2026-2034 phase-in and that origin_carbon_price_eur_per_tonne is a deductible credit rather than a reporting field. It reinforces that certificate_price_eur is caller-supplied and will not be invented, which matters for preventing fabricated market prices.

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 (computes) and a specific resource (CBAM certificate cost of importing goods into the EU), pinning it to Regulation (EU) 2023/956 as amended by 2025/2083 and Directive 2023/959 Art. 10a(1a). The scope is unmistakable against the regulatory-classification siblings (csrd_scope, eu_ai_act_classify, compliance_deadlines, uae_corporate_tax), none of which compute a cost figure.

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?

Rich trigger guidance: it enumerates the concrete user questions that should route here (per-tonne cost, landed-cost impact, deduction of origin carbon price, free-allocation phase-out) and explicitly says to use it rather than estimating because the phase-in factor is commonly miscalculated. What it lacks is an explicit negative boundary, e.g. when a deadline/scope question belongs to compliance_deadlines instead of here.

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