Супермаркет САМПО

quote_cart

Итог корзины по текущим ценам и остатку. Заказ не создаёт. Без авторизации. Тело — объект lines: массив строк {goods_id, min_qty, cards}.

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": {
      "lines": "<lines>"
    },
    "name": "quote_cart"
  }
}

Input Schema

Name	Required	Description
`city`	No	Город
`mode`	No	pickup, city или distant. Пусто — только товары
`house`	No	Дом
`lines`	Yes	Строки: goods_id, min_qty ступени, cards — сколько таких упаковок
`street`	No	Улица
`service`	No	cdek или dostavista
`pvz_code`	No	Код пункта выдачи
`tariff_code`	No	Тариф СДЭК

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / properties / lines / items / properties / cards / description

Added value: +"Сколько таких упаковок. Пусто — одна"

addedInput schema / properties / lines / items / properties / goods_id / description

Added value: +"Идентификатор товара, как в адресе /catalog/{id}"

addedInput schema / properties / lines / items / properties / min_qty / description

Added value: +"Ступень с карточки: сколько штук в одной упаковке"

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description does real work by disclosing two key behavioral traits: no order is created (non-mutating) and no authorization is required. However, it says nothing about the shape of the result, error behavior, or how delivery parameters affect the quote, which the absent annotations leave entirely uncovered.

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?

Telegraphic and front-loaded: purpose first, then the two exclusions, then the body shape. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, no-annotation, no-output-schema tool, the description covers purpose, side effects, auth, and the required body, but omits the return value structure (only 'Итог корзины' is given) and leaves the entire delivery-parameter group unaddressed.

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 baseline applies. The description restates the lines structure (goods_id, min_qty, cards) already fully documented in the schema, and adds no semantics for city, mode, service, pvz_code, or tariff_code — the fields whose interdependence (e.g., mode=pickup vs distant) is least obvious.

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 operation (computing cart totals from current prices and stock) and immediately disambiguates it from the checkout sibling with 'Заказ не создаёт,' so an agent can tell it apart from create_checkout and check_stock without opening the schema.

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 exclusion 'Заказ не создаёт' and 'Без авторизации' imply this is a pre-order pricing call, but no alternative is named explicitly and there is no explicit when-to-use instruction. Usage is inferable rather than stated.

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.

Resources

Need Help?