Skip to main content
Glama

taric_hs_validator

Read-onlyIdempotent

[Deterministic customs tariff calculation. Pure calculation, read-only, side-effect free]. Validates 6, 8, and 10-digit TARIC / Combined Nomenclature codes, calculates CIF customs valuation (goods price + international freight/insurance to EU border), computes third-country import duty payable, and determines border VAT base. Usage: Use this tool to calculate statutory customs duties and import VAT before shipping goods to the EU. For Incoterms cost splitting across parties, use 'incoterms_cost_allocator'. Returns: JSON object with { taricCode: string, cifCustomsValueEur: number, dutyRatePercent: number, dutyPayableEur: number, importVatPayableEur: number, totalBorderTaxesEur: number }.

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) (e.g. 7208100000, 85423190)
customsValueEurYesInvoice value of imported goods in EUR
countryOfOriginIso2YesCountry of origin 2-letter ISO code (e.g. CN, US, GB)
importVatRatePercentNoApplicable import VAT rate percentage (default: 22%)
freightAndInsuranceEurNoFreight and insurance costs to EU border in EUR
dutyRateOverridePercentNoSpecific duty rate percentage if preferential tariff applies

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / countryOfOriginIso2 / description
      Previous value: -"Country of origin 2-letter ISO code"New value: +"Country of origin 2-letter ISO code (e.g. CN, US, GB)"
    • changedInput schema / properties / dutyRateOverridePercent / description
      Previous value: -"Specific duty rate percentage if known"New value: +"Specific duty rate percentage if preferential tariff applies"
    • changedInput schema / properties / importVatRatePercent / description
      Previous value: -"Applicable import VAT rate percentage"New value: +"Applicable import VAT rate percentage (default: 22%)"
    • changedInput schema / properties / taricCode / description
      Previous value: -"TARIC code (6, 8, or 10 digits)"New value: +"TARIC code (6, 8, or 10 digits) (e.g. 7208100000, 85423190)"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, and the description reinforces determinism and side-effect freedom rather than adding new safety information. Where it does add value is the explicit return-shape block (taricCode, cifCustomsValueEur, dutyRatePercent, dutyPayableEur, importVatPayableEur, totalBorderTaxesEur), which matters because no output schema exists. The notable gap is what happens when a TARIC code fails validation — the tool 'validates' but the declared response has no validity flag, so error behavior is undisclosed.

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?

Front-loaded bracket states what the tool is, then Usage, then Returns — a predictable scan pattern with no wasted sentences. The bracketed preamble partly restates the annotations, and the long comma chain in the opening sentence could be tighter, but nothing is filler given the absent output schema.

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?

With six parameters, full schema coverage, and no output schema, the definition supplies the return contract, the sibling alternative, and the CIF formula — enough to call it correctly. The remaining gap is failure semantics for invalid TARIC codes and rate-lookup misses, which an agent computing statutory amounts would want to know before relying on the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns extra by defining CIF as 'goods price + international freight/insurance to EU border', which clarifies how customsValueEur and freightAndInsuranceEur combine into the returned cifCustomsValueEur. It still says nothing about when dutyRateOverridePercent (preferential tariff) should be supplied versus left to lookup, which is the parameter most likely to be misused.

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 names four concrete operations — validating 6/8/10-digit TARIC codes, computing CIF customs value, computing third-country duty, and determining the border VAT base — with the verb+resource pairing stated explicitly. It also distinguishes itself from incoterms_cost_allocator, so an agent can tell which tool handles statutory duties versus cost allocation without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the use context ('calculate statutory customs duties and import VAT before shipping goods to the EU') and names an explicit alternative with the condition that selects it ('For Incoterms cost splitting across parties, use incoterms_cost_allocator'). The routing decision is fully resolved in the text.

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