CBAM Data

Check Annex I Scope

cbam_scope

Read-onlyIdempotent

Check whether a Combined Nomenclature (CN) code falls within Annex I of Regulation (EU) 2023/956, and inspect sector coverage, direct/indirect rules, or child sub-headings.

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>"
    },
    "name": "cbam_scope"
  }
}

Input Schema

Name	Required	Description	Default
`cn`	Yes	CN or TARIC code at 4, 6, 8, or 10 digits (e.g. 7208, 72083900).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful domain context by saying the tool can inspect sector coverage, direct/indirect rules, and child sub-headings, but it does not explain response shape or limits.

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 with the scope-check purpose front-loaded and no redundant wording. It is appropriately sized for a one-parameter lookup tool.

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 simple read-only lookup, the description conveys the core check and hints at additional returned details. However, with no output schema, it could more clearly state what the response contains (e.g., boolean plus sector/subheading information), leaving some ambiguity for the agent.

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% for the single cn parameter, including accepted digit lengths and examples. The description adds no syntax or format meaning beyond what the schema already provides, so the baseline of 3 applies.

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?

States a specific verb ('Check whether') and resource (CN code) tied to Annex I of Regulation (EU) 2023/956, making the core purpose unambiguous. It distinguishes itself from sibling tools by being the scope-check operation, but does not explicitly name an alternative for contrast.

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 explicit when-to-use or when-not guidance, and no mention of siblings such as cbam_resolve or cbam_defaults. The intended use is implied by the purpose, but the agent must infer when this tool is preferred over alternatives.

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

All CBAM Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?