Skip to main content
Glama

DataCastle EU Compliance & Customs

datacastle_verify_taric_code

Validates an EU 8-to-10 digit TARIC / HS Customs Classification Code. Verifies chapter hierarchy, numerical syntax, checks against EU customs nomenclature, and audits alignment with provided goods description.

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": {
      "tariffCode": "<tariffCode>",
      "goodsDescription": "<goodsDescription>"
    },
    "name": "datacastle_verify_taric_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
tariffCodeYesThe 8-digit CN or 10-digit TARIC code (e.g. '8481.20.90' or '8481209000').
goodsDescriptionYesCommercial description of the imported/exported merchandise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the four validation dimensions performed, which is meaningful behavioral detail beyond the name. It does not state whether any external EU nomenclature lookup occurs, whether results are pass/fail or a detailed report, or how invalid codes are reported—gaps for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with the core action, and every clause names a distinct check performed. No filler or redundant restatement of the tool name.

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 two-parameter, non-mutating validation tool whose schema is fully documented, the description is nearly sufficient. The remaining gap is that no output schema exists and the description never indicates what a result looks like (validity flag, failing check, error message), which an agent would want to interpret the response.

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 coverage is 100% and both parameters are documented with formats and an example ('8481.20.90' or '8481209000'), so the baseline is 3. The description's mention of '8-to-10 digit' and 'goods description' only restates what the schema already says, adding no new semantics such as accepted separators or length-mismatch behavior.

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?

The description opens with a specific verb ('Validates') and a precise resource ('EU 8-to-10 digit TARIC / HS Customs Classification Code'), then enumerates the exact facets checked: chapter hierarchy, numerical syntax, EU nomenclature, and goods-description alignment. This is clearly distinguishable from siblings like customs document audit or freight reconciliation without inspecting schemas.

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 implies usage—validate a code against a goods description—but never states when to call it versus the sibling audit/compliance tools, nor any prerequisites such as needing the code in a specific format before calling. Usage must be inferred from the purpose statement alone.

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.