Skip to main content
Glama

Xonta Customs RU

tnved_search

Read-onlyIdempotent

Search the TN VED EAEU (ТН ВЭД ЕАЭС) commodity nomenclature by product words or code prefix.

Returns candidate 10-digit codes with official names and the ETT import duty rate.
Use the candidates to pick a code, then call tnved_code_info for details.
Text search matches nomenclature wording, so use technical terms (material, function),
not brand names. Results are candidates, not a classification decision.

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": {
      "query": "<query>"
    },
    "name": "tnved_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryYesProduct description in Russian (e.g. 'насос шестеренный гидравлический') or a code prefix like '8413' or '8413603100'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description only needs to add what annotations cannot say. It does: the return payload (10-digit codes, official names, ETT import duty rate) and the important caveat that hits are candidates rather than a classification ruling. Only the behavior of the match itself (exact vs. fuzzy, ranking) is left unstated.

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?

Four short lines, front-loaded with the action and the resource, then return shape, then next step, then query advice. Every sentence carries information; the only minor redundancy is the bilingual parenthetical in the opening line.

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?

There is no output schema, so the description correctly takes on the burden of describing what comes back (codes, names, duty rate). Combined with the schema's documented query and limit parameters, an agent has everything needed to call it; only result-set behavior such as ordering or truncation is unaddressed.

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 the schema already documents both parameters, which sets a baseline of 3. The description goes beyond it by explaining that matching is on nomenclature wording and that technical terms (material, function) work better than brand names, which is real query-construction guidance not present in the schema.

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 definition states a specific verb and resource ("Search the TN VED EAEU commodity nomenclature") plus the two accepted input forms (product words or code prefix). It is clearly distinct from the sibling tnved_code_info, which is named as the follow-up step rather than the same operation.

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?

It gives explicit routing: search first, pick a candidate, then call tnved_code_info for details. It also names its limits as a candidate generator ("Results are candidates, not a classification decision") and tells the agent how to phrase queries, which is when-to-use guidance at the phrasing level.

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.