Skip to main content
Glama

Xonta Customs RU

calc_recycling_fee

Read-onlyIdempotent

Recycling fee (утилизационный сбор) for a passenger car (category M1) imported into Russia.

Uses the official coefficient table (Decree 1291 as amended by Decree 1713 of 01.11.2025):
base rate 20 000 RUB x coefficient by engine type, volume, power band (kW), age and year
(Dec 2025, 2026 ... 2030). Covers the commercial table and the personal-use table
(0.17 / 0.26 for up to 160 hp and up to 3 l). Returns the coefficient, band and 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": {
      "engine": "<engine>"
    },
    "name": "calc_recycling_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
engineYesice = petrol/diesel; hybrid_parallel counts as ICE; ev = electric; hybrid_series = series hybrid (counts as EV)
on_dateNoDate YYYY-MM-DD the fee is calculated for; default today. Tables run Dec 2025 - 2030
power_hpNoEngine power in horsepower (л.с.); for EVs the 30-minute max power
power_kwNoEngine power in kW, alternative to power_hp
personal_useNoImported by an individual for personal use (preferential 3 400 / 5 200 RUB up to 160 hp and 3 l)
eaeu_extra_rubNoFor cars released in another EAEU country: sum of Ктп + Кндс + Ка (duty, VAT, excise differences), if known
engine_volume_ccNoEngine displacement in cm3 (required for ice and hybrid_parallel)
older_than_3_yearsNoTrue if more than 3 years have passed since the production date

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 readOnly, idempotent, closed-world, non-destructive behavior, so safety needs no restating. The description adds genuinely useful transparency: the calculation is table-driven with a 20 000 RUB base rate, the tables are versioned by date from Dec 2025 through 2030, and the result includes coefficient, band and source — which tells the agent the output is auditable.

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?

Roughly three sentences, front-loaded with the verb and resource before the legal citation and formula. The dense parenthetical enumerations (engine type, volume, power band, age, year) are efficient rather than padded, though the trailing fragment 'Returns the coefficient, band and source' could be folded into the preceding sentence.

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 usefully states the return contents (coefficient, band, source) and notes the date coverage window. For an eight-parameter financial calculator with full schema documentation, the main remaining gap is edge behavior — dates outside 2025–2030, and the interaction between personal_use, power and volume thresholds.

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 every parameter is already documented in detail, giving a baseline of 3. The description adds the underlying formula (base rate × coefficient by engine type, volume, power band, age, year) and cites the 0.17 / 0.26 personal-use coefficients, which gives context for the preferential mode but does not resolve ambiguities such as power_hp vs power_kw precedence or behavior for out-of-range dates.

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 (calculating the recycling fee / утилизационный сбор) and narrows scope precisely to M1 passenger cars imported into Russia. The legal basis (Decree 1291 as amended by 1713) further pins down exactly which calculation this performs, distinguishing it from generic payment calculators.

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?

Implies usage through scope statements (imported M1 passenger cars, commercial vs personal-use tables, Dec 2025–2030 tables), which lets an agent infer when it applies. However, it never names an alternative such as calc_import_payments for duties/VAT/excise, even though the eaeu_extra_rub parameter shows those calculations live elsewhere, and it gives no explicit when-not guidance.

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.