Skip to main content
Glama

tnved_search

Read-onlyIdempotent

Search EAEU TN VED commodity codes by product keywords or code prefix to get 10-digit candidates with official names and import duty rates for classification.

Instructions

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 observedv0.2.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: it discloses the return payload (candidate 10-digit codes, official names, ETT import duty rate) and the important interpretive caveat that matches are candidates rather than rulings. It stops short of stating how many candidates are typical or how ranking works, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the action and query modes, followed by return shape, the follow-up tool, and the caveat. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only two parameters, the description carries the necessary burden: it covers input semantics, returned fields, and the downstream tool to call. An agent has everything needed to invoke it correctly and interpret results.

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 baseline is 3; the description still adds meaning by specifying that queries should be Russian technical vocabulary (material, function) or a code prefix, reinforcing the schema's example. The limit parameter is left to the schema with no guidance on when to raise it.

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?

Names a specific verb plus resource ('Search the TN VED EAEU commodity nomenclature') and states both accepted query modes (product words or code prefix). An agent can immediately distinguish it from tnved_code_info, which is explicitly framed as the follow-up detail lookup.

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?

Gives explicit when-to-use ('text search matches nomenclature wording, so use technical terms... not brand names'), names the alternative and the handoff sequence ('Use the candidates to pick a code, then call tnved_code_info for details'), and adds a scope caveat that results are not a classification decision.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.