Skip to main content
Glama

Xonta Customs RU

tnved_code_info

Read-onlyIdempotent

Get everything known about one TN VED EAEU code.

Returns the official name with parent headings, the ETT import duty rate parsed into ad valorem / specific / combined parts, EAEU antidumping measures that may apply (filtered by origin country if given) and EEC classification rulings for this heading.

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": {
      "code": "<code>"
    },
    "name": "tnved_code_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesTN VED EAEU code, 4-10 digits, spaces allowed, e.g. '8413 60 310 0'
origin_countryNoISO 3166-1 alpha-2 country of origin, e.g. 'CN', to check antidumping measures

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds meaningful content beyond that by detailing exactly which data domains are returned (name hierarchy, parsed duty components, country-filtered antidumping measures, classification rulings). What it does not cover is edge behavior: what happens for an invalid/nonexistent code, whether a 4-digit heading yields partial or aggregated results, or whether missing rulings simply return empty.

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 with a one-line purpose, followed by a compact enumeration of returned sections. No filler or marketing language; the line breaks make the payload scannable. Slightly longer than strictly necessary but every clause carries information.

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 no output schema, the description correctly takes on the burden of describing the return payload by naming all four result sections. It is nearly complete for an aggregation read tool, with the only gap being undefined behavior for invalid codes or non-existent headings, which matters for an agent that must decide whether to retry or escalate.

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

Parameters2/5

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

Schema coverage is 100% and both parameters are fully documented in the input schema, including the digit range, space tolerance, example, and ISO 3166-1 alpha-2 requirement for origin_country. The description merely restates the filtering behavior ("filtered by origin country if given") without adding any new semantics, so it sits below the baseline rather than at it.

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 and resource ("Get everything known about one TN VED EAEU code") and enumerates the payload: official name with parent headings, ETT duty rate split into ad valorem/specific/combined, antidumping measures, and EEC classification rulings. That enumeration implicitly differentiates it as a per-code aggregator versus tnved_search, antidumping_check, and classification_rulings_search, but it never names or contrasts those siblings explicitly.

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?

Usage is only implied: you use it when you already hold a code and want the consolidated picture. There is no explicit when-to-use statement, no guidance on when to call the narrower sibling tools instead, and no note on whether origin_country should be supplied routinely or only for known-suspect origins.

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.