Skip to main content
Glama

Xonta Customs RU

antidumping_check

Read-onlyIdempotent

Check EAEU trade defence measures (antidumping duties) by code, product and origin country.

Returns matching measures with the Eurasian Economic Commission decision, the decision that
sets duty rates per producer, expiry date and a link. The bundled list covers measures
renewed in 2026 and is not exhaustive: absence of a match is not proof that no measure applies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "antidumping_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoTN VED EAEU code or prefix
productNoProduct words in Russian or English, e.g. 'грузовые шины'
origin_countryNoISO alpha-2 country of origin, e.g. CN, UA, AZ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds real value: it describes the returned fields (Commission decision, per-producer duty rates, expiry date, link) and warns that absence of a match is not proof that no measure applies. The remaining gap is that all three parameters are optional, yet the description never says how they combine or whether at least one is needed.

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?

Purpose is front-loaded in the first sentence, followed by return contents and a caveat, with no filler. The second sentence is dense but each clause carries information an agent needs.

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, and the description compensates by enumerating the returned fields, plus it flags the non-exhaustive coverage limitation. Only the handling of optional parameters and matching behavior remains unspecified.

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%, with each parameter documented including examples (TN VED code or prefix, Russian/English product words, ISO alpha-2 origin). The description repeats the three dimensions without adding format, matching or combination semantics beyond what the schema already carries, so the baseline of 3 applies.

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 names a specific verb and resource, 'Check EAEU trade defence measures (antidumping duties)', and scopes it by code, product and origin country. That is clearly distinct from the classification and payment calculators among its siblings, though no sibling is named as an alternative.

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 implied by the scope statement rather than stated: an agent can infer to call it when verifying whether duties apply to a good. There is no explicit when-not guidance and no direction to alternatives such as tnved_search or tnved_code_info for code resolution, so guidance stays at the implied 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.