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

create_checkout

Создать заказ и ссылку на страницу банка. Нужен вход пользователя и scope checkout. Телефон клиента берётся из его аккаунта. Цена и остаток считаются заново. Повтор с тем же idempotency_key возвращает тот же заказ.

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": {
      "idempotency_key": "<idempotency_key>",
      "lines": "<lines>",
      "mode": "<mode>",
      "name": "<name>",
      "personal_data": "<personal_data>"
    },
    "name": "create_checkout"
  }
}

Input Schema

Name	Required	Description
`city`	No	Город
`flat`	No	Квартира
`mode`	Yes	pickup, city или distant
`name`	Yes	Имя получателя
`slot`	No	Слот Достависты
`email`	No	Почта
`house`	No	Дом
`lines`	Yes	Строки: goods_id, min_qty ступени, cards — сколько таких упаковок
`phone`	No	Не передавайте. Телефон берётся из аккаунта вошедшего клиента и обязателен
`region`	No	Регион
`street`	No	Улица
`comment`	No	Комментарий
`service`	No	cdek или dostavista
`pvz_code`	No	Код пункта выдачи
`postal_code`	No	Индекс
`tariff_code`	No	Тариф СДЭК
`personal_data`	Yes	Согласие на обработку данных: 1
`idempotency_key`	Yes	Ключ повтора, до 80 символов

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.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses important behavior: authentication and scope requirements, phone sourcing from account, price/stock recalculation, and idempotent repeat semantics. It still omits payment-link lifecycle, failure behavior, and reversibility details, so it is strong but not complete.

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?

The description is short, front-loaded with the core action, and each sentence adds useful information about auth, phone sourcing, recalculation, or idempotency. There is no filler.

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 an 18-parameter mutation tool with no annotations and no output schema, it covers the core prerequisites and side-effect semantics well. Return-value details and failure/payment-link behavior are thin, but the rich input schema covers the parameter surface.

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%, so the schema already documents the 18 parameters and the baseline is 3. The description adds useful idempotency-key repeat semantics, but the phone guidance largely duplicates the schema and most address/delivery parameters receive no extra meaning beyond schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: create an order and a bank payment-page link. This is clearly distinct from sibling tools like quote_cart or get_order_status, but it does not explicitly name or differentiate against those siblings.

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?

It gives clear prerequisites: user login and checkout scope are required, and phone is taken from the account. However, it does not say when to use this instead of quote_cart or get_delivery_options, nor does it state exclusions or ordering constraints.

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?