Skip to main content
Glama
nohosa001-pixel

EUDR Compliance & TRACES-NT Agent

by nohosa001-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

eudr_evaluate_customs_taric

Evaluate a commodity HS code and EUDR status to determine the required EU TARIC Document Code (C081, C082, Y120–Y122) and format Box 44 customs declaration fields.

Instructions

Evaluates commodity HS code and regulatory status to determine the statutory EU TARIC Document Code (C081, C082, Y120, Y121, Y122) and formats Box 44 / DE 12 03 000 000 customs declaration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hs_codeYesHarmonized System tariff code (6-10 digits).
is_recycledNoWhether 100% post-consumer recycled waste (Annex I Footnote 1).
dds_reference_idNoTRACES-NT DDS reference number, if already filed.
is_packaging_onlyNoWhether commodity is protective packaging supporting another good.
verification_codeNoTRACES-NT security verification code.
is_downstream_operatorNoWhether downstream operator referencing upstream DDS (Art. 4(8)).
upstream_dds_referenceNoUpstream DDS reference for pass-through.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the output (a TARIC code and formatted declaration), but omits safety profile, read-only vs write behavior, authentication requirements, side effects, and error handling.

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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose and output without redundancy.

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 tool with no output schema, the description adequately identifies the return content (statutory TARIC code and Box 44 formatting). Combined with rich schema coverage for all parameters, an agent has enough to call it, though usage context and behavioral details remain thin.

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 the schema fully documents all seven parameters. The description adds no parameter-level syntax or format details beyond what the schema already provides, making the baseline score of 3 appropriate.

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 states a specific evaluation task (HS code plus regulatory status) and names the exact output codes (C081, C082, Y120, Y121, Y122) and declaration format (Box 44 / DE 12 03 000 000). This clearly distinguishes it from siblings like eudr_generate_customs_certificate or eudr_simulate_swe_c_customs_clearance.

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?

No explicit when-to-use guidance or alternatives are provided. The description implies usage for customs declaration preparation, but does not state conditions, prerequisites, or when another sibling tool would be more appropriate.

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