Skip to main content
Glama

Extreme Drive — extreme driving school

Оформить заказ

create_order

Создаёт заказ Extreme Drive по полям корзины, без пошагового визарда. Обязательны items, email, delivery, payment, buyer, agree_oferta=true, agree_privacy=true. buyer: first_name и телефон; достаточно одного имени — фамилия (last_name) необязательна, не настаивайте на ней. Оферта: https://www.extrimdrive.ru/club/oferta2025_new.pdf политика конфиденциальности: https://www.extrimdrive.ru/docs/confidentiality.php. Для ПВЗ укажите ближайший пункт обычным адресом/текстом — без проверки Яндекс.Доставки; менеджер подтвердит или заменит. Карточные данные не принимаются. Если payment не courier, в ответе будет payment_url на extrimdrive.ru, по которому человек переходит в эквайринг (карта / СБП / Сплит). Если payment=courier (только вместе с delivery.type=pvz), ссылки нет: заявка принята, менеджер позвонит. Участник каждого сертификата: participants[] (если не указан, копируется покупатель). Логин не требуется.

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": {
      "items": "<items>",
      "email": "<email>",
      "delivery": "<delivery>",
      "payment": "<payment>",
      "buyer": "<buyer>",
      "agree_oferta": "<agree_oferta>",
      "agree_privacy": "<agree_privacy>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
emailYesE-mail покупателя (ya.ru заменяется на yandex.ru)
itemsYesПозиции: type=course|program, id или course_id/program_id, quantity, необязательно with_rent=true
is_giftNo
paymentYesvisa карта, alpha СБП/QR, yapay Сплит 6 месяцев, courier карта в ПВЗ
deliveryYestype: online | pvz | offline | runner
gift_dateNo
class_dateNoЖелаемая дата занятия; запись необязательна, как на сайте
promo_codeNoПромокод, если он действует на сайте
school_carNoМарка учебной машины, если хотя бы у одной позиции with_rent=true
agree_ofertaYesСогласие с офертой /club/oferta2025_new.pdf
participantsNoПо одному участнику на каждую единицу сертификата (включая курсы внутри программы). Если элемент опущен, копируется покупатель.
agree_privacyYesСогласие с политикой /docs/confidentiality.php
email_receiptNoЭлектронный чек на e-mail (для оплаты картой, как на сайте)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the generic write profile (readOnlyHint=false, idempotentHint=false); the description adds real operational detail beyond that: card data is rejected, a payment_url is returned for all non-courier payments, courier payment returns no link and relies on a manager callback, participants default to a copy of the buyer, and no login is required. These are exactly the side effects and follow-up expectations an agent needs before invoking a non-idempotent write.

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 mandatory-field list is front-loaded, which is good, but the remainder is a dense run-on paragraph mixing consent URLs, payment branching, PVZ handling and participant defaults in no clear order. Every sentence carries information, yet the lack of grouping makes it harder to scan than it needs to be for a 14-parameter tool.

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 14-parameter nested write with no output schema, the description covers the essentials: required inputs, the consent requirements, the conditional payment_url return value, and the courier exception. Minor gaps remain around failure behavior (what happens on invalid promo code or unavailable rent) and whether the order is confirmed or pending manager approval outside the courier case.

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 description coverage is high (79%), so the schema already carries most parameter meaning and the baseline is 3. The description still adds value where the schema does not: that first_name plus phone suffice and last_name must not be insisted upon, that the offerta/privacy flags are mandatory consents with document URLs, and that PVZ addresses are free text accepted without validation.

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 opening states a specific verb and resource ('Создаёт заказ Extreme Drive') and adds a distinguishing scope note ('по полям корзины, без пошагового визарда'), which tells an agent this is a single-shot write rather than a multi-step flow. It does not explicitly name a sibling, but the surrounding get_*/list_* tools are read operations, so the write intent is unambiguous.

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?

It gives concrete usage context: required fields are enumerated, PVZ delivery should be a plain-text nearest pickup point with no Yandex.Delivery check, and courier payment is only valid together with delivery.type=pvz. What it lacks is explicit routing against alternatives (e.g. 'check availability with get_course first' or 'use get_order to confirm'), so an agent knows how to call it but not the surrounding workflow.

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.

Resources