Skip to main content
Glama
Keremozdemirra

cbam-mcp

by Keremozdemirra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

CBAM scope of a CN code

cbam_scope
Read-onlyIdempotent

Check if goods under a CN code fall within EU CBAM scope. Returns in_scope, partially_in_scope, or not_in_scope with reasons from Annex I.

Instructions

Whether goods under a CN code are in the scope of the EU Carbon Border Adjustment Mechanism, from Annex I of Regulation (EU) 2023/956 as amended by Regulation (EU) 2025/2083 (consolidated text of 2025-10-20). Returns status 'in_scope', 'partially_in_scope' or 'not_in_scope' with the reason; the deciding Annex I line (goods category, greenhouse gases, exceptions, 'ex' flag); whether Annex II limits the goods to direct emissions; the de minimis texts (Article 2a, Annex VII) where they apply; the CN 2026 description. 'partially_in_scope' means an 'ex' line (only part of the code is covered: read the line's text) or a heading whose sub-codes differ. For codes shorter than 8 digits it lists the CN 2026 sub-codes in and out of scope (up to limit per list). Not legally binding; information, not legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNosub-codes listed per status, default 50
cn_codeYesCN code, 2 to 8 digits (or a 10-digit TARIC code), with or without spaces or dots: '7208 51 20', '72085120', '7208.51.20', '7208'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower. The description adds real behavioral context: the meaning of each status value, that 'ex' lines split codes, that short codes enumerate sub-codes capped by `limit`, and that results are informational, not legally binding.

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

Conciseness3/5

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

Front-loaded and information-dense, but the middle sentence is a long run-on enumerating every return field, and the legal-source parenthetical adds bulk. Every clause carries information, yet the packed structure reduces readability.

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 single-code lookup with no output schema, the description fully enumerates the returned fields, the status semantics, the 'ex'-line edge case, the short-code sub-code listing, and the de minimis provisions. Nothing an agent needs to invoke or interpret the result is missing.

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 both parameters (cn_code format with/without separators, and limit) are fully documented in the schema. The description adds context on how `limit` interacts with short codes but doesn't extend beyond what the schema already states. 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+resource: determining whether goods under a CN code fall within the EU CBAM scope, citing the exact legal source (Annex I of Reg. 2023/956 as amended). This is clearly distinct from siblings like cn_describe (code description) and compare_origins (origin emission comparisons).

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?

The description explains what it returns and how to interpret 'partially_in_scope', but never says when to reach for this tool vs siblings like cn_describe or default_value. Usage is implied by the purpose rather than stated.

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

Deploy Server

Other Tools