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

Регуляция целиком

get_regulation

Read-onlyIdempotent

Одно правило РФ целиком: ответ с суммами, таблица ставок (у утильсбора — мощность, коэффициент и сумма для новой машины и старше 3 лет), разделы, ссылки на акты, хронология. Идентификатор — из list_regulations (например utilization-fee-2025-12, subsidiya-925k). Сумму под конкретную мощность и возраст считает calc_import_fees. EN: one Russian EV rule in full: the answer with amounts, the rate table (recycling fee by power and age), sections, acts, timeline.

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": {
      "slug": "<slug>"
    },
    "name": "get_regulation"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Идентификатор регуляции из list_regulations

Output Schema

Name	Required	Description
`url`	Yes
`slug`	Yes
`rates`	No	Ставки утильсбора: база × коэффициент по 30-минутной мощности и возрасту
`terms`	Yes	Условия использования данных (адрес)
`title`	No
`answer`	No	Прямой ответ с суммами и актом
`status`	No
`sources`	No
`sections`	No
`timeline`	No
`markdown_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the response is structured into rate tables, sections, acts and a timeline, and the recycling-fee table is broken out by power and by vehicle age (>3 years vs new).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Russian text is front-loaded and dense, but the appended EN gloss restates the same content rather than adding anything, which is duplication in a definition that is already long. The parenthetical about the recycling-fee table is earned; the bilingual repeat is not.

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?

An output schema exists, so return values need not be explained, yet the description goes further and characterizes the response sections. With the single parameter documented in both schema and description and both relevant siblings named, nothing an agent needs in order to call this correctly is missing.

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 schema already says the slug comes from list_regulations, so the baseline is high. The description still adds value by giving concrete format examples (utilization-fee-2025-12, subsidiya-925k), which make the expected identifier shape obvious in a way the schema does not.

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?

"Одно правило РФ целиком" names a specific verb-scope and resource, then enumerates exactly what comes back (amounts, rate table, sections, acts, timeline). It is also explicitly differentiated from the two nearest siblings: list_regulations supplies the ID and calc_import_fees does the per-power/age computation.

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

Usage Guidelines5/5

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

The description states where the required slug comes from (list_regulations) and redirects the arithmetic case to calc_import_fees, so an agent knows both when this tool is right and which sibling to use instead. The only minor gap is that no exclusion for bulk listing is spelled out, but list_regulations is implicitly the counterpart.

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.