Skip to main content
Glama

Приём оплаты в опросе

manage_quiz_payment
Destructive

Приём оплаты в опросе через ЮKassa. show — текущие настройки, список счетов продавца аккаунта (без секретных токенов) и виды расчёта суммы. save — выбрать счёт, задать вид расчёта (фиксированная сумма или сумма по набранным баллам), саму сумму и вопрос, из которого берут контакт для чека. Счета продавца здесь не заводятся и не правятся: для них нужны идентификатор магазина и секретный токен ЮKassa, а платёжные ключи через ассистента не передают — это делают в кабинете. Отдельного переключателя «включить оплату» нет: оплата работает, когда у аккаунта есть счёт продавца и тариф разрешает виджет оплаты, а показ самого вопроса с оплатой задаётся его виджетом через update_quiz_widgets.

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": {
      "quiz_id": "<quiz_id>",
      "action": "<action>"
    },
    "name": "manage_quiz_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: show — настройки и счета, save — сохранить настройки.
quiz_idYesID опроса.
fixed_amountNoСумма к оплате. Обязательна при fixed: без неё оплата ушла бы на ноль.
payment_typeNoКак считается сумма: fixed — фиксированная, scoring — по набранным баллам. Обязателен для action=save.
contact_widget_idNoID вопроса, из которого берут контакт для чека (почта или телефон). Взять из quiz://{id}/structure. null — не брать.
yookassa_account_idNoID счёта продавца из show. Обязателен для action=save. Чужой счёт увёл бы платежи другому продавцу, поэтому проверяется принадлежность аккаунту.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent writes, and the description adds real context beyond them: show returns accounts without secret tokens, accounts cannot be created or edited here, and payment activation depends on account plus tariff. The one gap is that it never says save overwrites existing payment settings, which is exactly the destructive behavior the annotation warns about.

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?

It is front-loaded with the tool's purpose, then the show/save semantics, then prerequisites and the sibling for widget display. The sentences are long and dense, but each carries an actionable constraint rather than 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 a mutating two-mode tool with no output schema, it covers what show returns, what save writes, ownership checking of the seller account, and where adjacent responsibilities live. It stops short of naming failure conditions or stating that save replaces prior configuration, the one omission that matters for a destructive write.

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%, so the baseline is 3, but the description adds meaning: payment_type selects between a fixed sum and a sum derived from earned points, yookassa_account_id comes from show, and contact_widget_id is the question supplying the receipt contact. Conditions (payment_type required for save, fixed_amount needed for the fixed type) are reinforced in prose.

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?

The description states a specific resource (payment acceptance in a quiz via YuKassa) and splits the tool's two modes (show/save) with concrete contents for each. It explicitly differentiates from update_quiz_widgets, which governs display of the paid question, so an agent can tell which tool owns which concern.

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?

It gives explicit routing: use show for current settings and the seller-account list, save for persisting account/type/amount/contact-question; account creation and secret-token entry belong in the cabinet, not here; question display belongs to update_quiz_widgets. It also states there is no separate 'enable payment' toggle, preventing a wasted call.

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