Skip to main content
Glama

Xonta Customs RU

customs_clearance_fee

Read-onlyIdempotent

Customs clearance fee (сбор за таможенные операции) for an import declaration into Russia in 2026.

The fee depends on the total customs value of the declaration: from 1 231 RUB (up to 200 000)
to 73 860 RUB (over 10 million). Also returns the full bracket table and the legal source.

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": {
      "total_customs_value_rub": "<total_customs_value_rub>"
    },
    "name": "customs_clearance_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
total_customs_value_rubYesTotal customs value of all goods in the declaration, RUB

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, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds real value beyond that: the fee is a function of total customs value, the output range runs from 1 231 RUB to 73 860 RUB, and the response also includes the full bracket table and the legal source. What remains undisclosed is rounding/formatting of the returned amount.

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?

Two short sentences, front-loaded with the resource and jurisdiction, followed by the value-dependency and output contents. The parenthetical Russian legal term and the numeric range both earn their space; nothing is redundant.

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 carries the burden of describing returns, and it does so by naming the fee, the bracket table, and the legal source. It is essentially complete for a one-parameter calculator; only minor details such as currency formatting or rounding rules are absent.

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% and the single parameter is already documented, so the baseline would be 3. The description goes further by explaining the dependency relationship: the fee is determined by the total customs value of the whole declaration, and it anchors the parameter's magnitude with concrete bracket boundaries (up to 200 000 vs over 10 million).

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 resource and verb: the customs clearance fee (сбор за таможенные операции) computed for an import declaration into Russia, 2026 edition. The resource is narrow enough that it is clearly distinct from siblings like calc_recycling_fee or calc_import_payments, though those siblings are never named, so the agent must infer the boundary from the domain wording alone.

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?

The description embeds usage context (import declaration into Russia, 2026, total declaration value) which implies when to call it, but it never states when not to call it or which sibling to use for adjacent fees such as recycling or import payments. Guidance is implied rather than explicit.

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.