Skip to main content
Glama

Xonta Customs RU

calc_import_payments

Read-onlyIdempotent

Calculate import customs payments into Russia for one goods item, in RUB.

Computes: import duty by the EAEU ETT rate (ad valorem, specific per kg/pcs/pair/litre,
or combined 'X%, but not less than Y EUR per unit'), antidumping duty, excise, import VAT
((customs value + duty + antidumping + excise) x 22% or 10%) and the 2026 customs clearance
fee by customs value bracket. Converts currencies at Bank of Russia rates.
Returns a line-by-line breakdown with sources.

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": {
      "customs_value": "<customs_value>"
    },
    "name": "calc_import_payments"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoTN VED EAEU code; its ETT duty rate is used if duty_rate is not given
on_dateNoDeclaration date YYYY-MM-DD for exchange rates; default today
currencyNoCurrency of customs_value: RUB, CNY, USD, EUR, etc.RUB
vat_rateNoImport VAT rate in 2026: 22 general, 10 for goods on Government lists (some food, children's goods, medical), 0 if exempt
duty_rateNoDuty rate as in the tariff, overrides the code: '10', '0', '0,6 евро за 1 кг', '15, но не менее 2,5 евро за 1 пару'
excise_rubNoExcise in RUB if the goods are excisable (alcohol, tobacco, fuel, cars)
quantity_lNoLitres
quantity_kgNoNet weight in kg, needed for per-kg specific rates
quantity_m2NoSquare metres
quantity_cm3NoEngine displacement in cm3
quantity_pcsNoPieces, for per-piece rates
customs_valueYesCustoms value of the goods (usually CIF to the EAEU border) in `currency`
quantity_pairNoPairs (footwear)
exchange_ratesNoRUB per 1 unit, e.g. {'CNY': 11.2, 'EUR': 92.5}. If omitted, Bank of Russia rates for `on_date` are fetched
recycling_fee_rubNoCar recycling fee (утильсбор) in RUB from calc_recycling_fee, to show the full cost of importing a vehicle. Not part of the VAT base
antidumping_rate_pctNoAntidumping/countervailing/special duty rate in % of customs value, if a measure applies

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description need not cover safety. It adds real behavioral content: the exact VAT base formula, the 22%/10% rates with their 2026 rationale, the bracket-based clearance fee, and that currencies are converted at Bank of Russia rates (an openWorld dependency backed by the openWorldHint annotation). It does not address failure modes such as a missing TN VED rate or an unavailable exchange-rate fetch.

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?

The first sentence front-loads the verb, jurisdiction, granularity and currency, and the second packs the computation chain into a single efficient sentence. It is dense but every clause (rates, VAT base, fee bracket, FX source, returned breakdown) conveys information an agent cannot get from the 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?

For a 16-parameter computational tool with no output schema, the description is nearly sufficient: it names the outputs ("line-by-line breakdown with sources") and the calculation dependencies. The remaining gap is coverage of edge cases, such as what happens when neither code nor duty_rate resolves a rate, or behavior for multiple goods items.

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%, so 16 well-documented parameters already carry their own semantics; the baseline of 3 applies. The description does not materially extend parameter meaning beyond noting currency conversion behavior and the duty-rate forms, which the schema already illustrates with the same examples.

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?

States a specific verb and resource ("Calculate import customs payments into Russia for one goods item, in RUB") and enumerates exactly which charges are computed, including duty, antidumping, excise, VAT and the clearance fee. This makes it distinguishable from siblings such as customs_clearance_fee and calc_recycling_fee, which cover only one of these components.

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 words "import ... into Russia for one goods item" and by the mention that recycling_fee_rub comes "from calc_recycling_fee," which hints at routing. However, there is no explicit statement of when to prefer this tool over antidumping_check or customs_clearance_fee, and no exclusion for exports, multiple items, or non-RUB destinations.

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.