Skip to main content
Glama

NovaPixel LexGrid

taric_hs_validator

Validates 10-digit TARIC codes, Combined Nomenclature hierarchy, CIF customs valuation, import duty and border VAT payable.

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": {
      "taricCode": "<taricCode>",
      "customsValueEur": "<customsValueEur>",
      "countryOfOriginIso2": "<countryOfOriginIso2>"
    },
    "name": "taric_hs_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
taricCodeYesTARIC code (6, 8, or 10 digits)
customsValueEurYesInvoice value of imported goods in EUR
countryOfOriginIso2YesCountry of origin 2-letter ISO code
importVatRatePercentNoApplicable import VAT rate percentage
freightAndInsuranceEurNoFreight and insurance costs to EU border in EUR
dutyRateOverridePercentNoSpecific duty rate percentage if known

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does usefully disclose the computation chain (CIF valuation feeding duty and VAT payable), which implies a pure calculation with no side effects, but it says nothing about what happens with an invalid or unmatched code, where duty rates come from, or how results are returned. Meaningful but incomplete disclosure.

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?

A single dense sentence with no filler, and the primary action is front-loaded before the list of computed items. It is efficient, though the comma-separated list format is terse enough that the relationship between the listed elements has to be inferred.

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?

With six parameters, no annotations, and no output schema, the description is only partially complete. It never describes the shape of the result (duty amount, VAT amount, validity verdict, breakdown) and is silent on currency and failure behavior, which an agent needs to interpret the call result. Adequate as a summary but not complete for a computation tool with no output schema.

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 baseline is 3. The description adds some meaning by framing the valuation as 'CIF', which explains why freightAndInsuranceEur belongs in the valuation base, and by grouping duty and VAT as outputs of the rate parameters. However, it says '10-digit TARIC codes' while the schema allows 6, 8, or 10 digits, creating a minor inconsistency rather than added clarity.

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?

The description opens with a specific verb ('Validates') applied to named resources: TARIC codes, CN hierarchy, CIF customs valuation, import duty, and border VAT. An agent can tell this is a customs-duty calculation/validation tool rather than an emissions or export-control tool. It stops short of naming or contrasting any sibling, so it lands at 4 rather than 5.

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-to-use guidance, no mention of prerequisites (e.g., needing an EU import scenario), and no routing to alternatives such as incoterms_cost_allocator or cbam_embedded_emissions. The usage context must be inferred entirely from the list of computed quantities.

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