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

Сравнение двух моделей

compare_models

Read-onlyIdempotent

Сравнение двух моделей: ответ первым абзацем, таблица параметров с источниками цен, частые вопросы, фото с автором и лицензией. Звать на «что взять, X или Y», «чем отличаются». Модели — через slug_a и slug_b. EN: compare exactly two models side by side; use it for 'X or Y' questions.

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_a": "<slug_a>",
      "slug_b": "<slug_b>"
    },
    "name": "compare_models"
  }
}

Input Schema

Name	Required	Description	Default
`slug_a`	Yes	Первая модель: Идентификатор модели (zeekr-001) или её название («Zeekr 001», «москвич 3е»)
`slug_b`	Yes	Вторая модель: Идентификатор модели (zeekr-001) или её название («Zeekr 001», «москвич 3е»)

Output Schema

Name	Required	Description
`url`	Yes
`terms`	Yes	Условия использования данных (адрес)
`models`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already declare this as read-only, idempotent, non-destructive and closed-world, so safety is covered. The description adds the answer shape (summary paragraph, parameter table with price sources, FAQ, photo with author and license), but since an output schema already exists this is partly redundant rather than essential behavioral disclosure.

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-loaded with the comparison purpose, then triggers, then parameter mapping, so an agent gets the essentials in the first sentence. It is somewhat busy, mixing a Russian description with an English restatement, but no sentence is wasted.

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 simple two-parameter, read-only comparison tool with a full output schema, annotations and fully described params, the description covers purpose, triggers and output shape. Nothing an agent needs in order to invoke it correctly 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 coverage is 100% and both parameters are already documented with format examples in the schema. The description only restates that the two models go in slug_a and slug_b, adding no new meaning about matching behavior or slug resolution.

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 ('Сравнение двух моделей', 'compare exactly two models side by side') and constrains the arity to exactly two, which immediately separates it from single-model siblings such as get_model and search_models.

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 in both Russian and English ('что взять, X или Y', 'чем отличаются', 'X or Y' questions), so an agent knows when to select it. It does not explicitly name the alternative tools to use for non-comparison lookups, which is the only remaining gap.

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.