Электроатлас

Утильсбор и растаможка

calc_import_fees

Read-onlyIdempotent

Расчёт утильсбора электромобиля по 30-минутной мощности (кВт или л.с.), возрасту (новый или старше 3 лет) и профилю ввоза (физлицо для себя или коммерческий); с таможенной стоимостью — вся растаможка: пошлина 15%, утильсбор, таможенный сбор, СБКТС (допущение 90 000 руб.) и итог без НДС и с НДС 22%. Те же ставки и формула, что в калькуляторе /calc. Звать на «сколько утильсбор за машину 300 л.с.», «сколько растаможить электромобиль за 3 млн». EN: Russian recycling fee for an EV by 30-minute power, age and import profile; with a customs value, the full import cost (duty, fee, VAT scenarios).

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": "calc_import_fees"
  }
}

Input Schema

Name	Required	Description
`used`	No	Машина старше 3 лет (по умолчанию false — новая)
`power_hp`	No	Мощность в л.с., если кВт неизвестны: переводится как 1 л.с. = 0,7355 кВт
`power_kw`	No	30-минутная мощность, кВт (из ОТТС или СБКТС, не пиковая). Нужна она или power_hp
`personal_use`	No	Физлицо ввозит для себя (по умолчанию true); false — юрлицо, ИП, перепродажа
`customs_value_rub`	No	Таможенная стоимость, руб. (необязательно): тогда считается вся растаможка

Output Schema

Name	Required	Description
`url`	Yes
`used`	No
`terms`	Yes	Условия использования данных (адрес)
`customs`	No
`power_hp`	No
`power_kw`	Yes
`util_rub`	Yes
`privileged`	No
`util_source`	No
`personal_use`	No
`regulation_url`	No
`util_coefficient`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/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 adds real substance beyond them: it scopes the tool to EVs only, discloses the cost components (15% duty, recycling fee, customs fee, СБКТС assumed at 90 000 руб.), and states totals are given both without and with 22% VAT. It also declares the rates match the /calc calculator, which tells the agent the numbers are authoritative rather than estimates.

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?

Front-loads the calculation target and its inputs before the example triggers, and each clause carries information. The trailing EN sentence largely duplicates the RU text, which costs a little space without adding new facts.

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 an output schema present, the description needn't explain return values, and it instead covers what matters for correct use: EV-only scope, the exact fee assumptions, VAT scenarios, and which inputs drive the result. Nothing an agent needs to call and interpret this tool is missing.

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 the schema already explains every parameter, including the hp-to-kW conversion factor and the 'new vs older than 3 years' meaning of `used`. The description restates those same three drivers rather than adding new semantics, so the baseline 3 applies.

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 ('Расчёт утильсбора электромобиля') plus the exact drivers used (30-minute power, age, import profile), and extends it to full customs clearance when a customs value is supplied. None of the siblings (compare_models, find_dealers, get_regulation, get_sales) overlap, so an agent can route unambiguously.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger phrasings ('сколько утильсбор за машину 300 л.с.', 'сколько растаможить электромобиль за 3 млн') that map directly to invocation contexts, and notes the optional customs value switches the tool into full-import mode. It does not name exclusions or alternatives, though the sibling set makes overlap unlikely.

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

All Электроатлас tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.