Skip to main content
Glama
theYahia

@theyahia/yookassa-mcp

by theYahia

Create payment

create_payment
Destructive

Create a YooKassa payment and get a confirmation URL for redirect, embedded, or QR confirmation. Supports one-step and two-step payments, receipts, and metadata.

Instructions

Create a payment in YooKassa. Returns a confirmation URL. Supports one-step and two-step payments, receipts, and metadata. MOVES REAL MONEY (the payer is charged) — irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesPayment amount in rubles (string '5000.00' for exactness, or a number)
captureNotrue = one-step (auto-capture), false = two-step (hold)
currencyNoCurrency (ISO-4217, default RUB)RUB
metadataNoArbitrary metadata (key-value)
return_urlNoURL to return the payer to after payment — REQUIRED when confirmation_type=redirect
descriptionYesPayment description (max 128 chars)
receipt_emailNoCustomer email for the receipt
receipt_itemsNoItems for a 54-FZ receipt (if issuing a receipt with the payment)
confirmation_typeNoConfirmation type: redirect (needs return_url), embedded (widget), or qrredirect
payment_method_typeNoPayment method
receipt_tax_system_codeNoReceipt tax system code, tag 1055 (only if the shop has multiple tax systems / FFD 1.2)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
paidNo
amountNo
statusNo
confirmation_urlNo
Behavior5/5

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

The description adds critical behavioral context beyond the annotations: 'MOVES REAL MONEY (the payer is charged) — irreversible.' This strongly reinforces the destructiveHint=true annotation and warns an agent of the non-reversible, financial impact. It also discloses the return of a confirmation URL, which the agent needs to know. The description is fully consistent with the annotations.

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 concise and front-loaded: it states the purpose in the first sentence, then returns the key output, lists supported features, and ends with a clear warning. Each sentence delivers essential information without fluff, and the warning is appropriately placed at the end for emphasis.

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

Completeness5/5

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

The description is complete given the rich schema, annotations, and output schema. It covers the main purpose, the confirmation URL, supported payment modes, and the irreversible money-movement warning. The schema handles parameter details and return values, so the description doesn't need to repeat them. For a complex payment tool, this is effectively complete.

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 schema already thoroughly documents all 11 parameters. The description mentions high-level features (one-step/two-step, receipts, metadata) that map to parameters but does not add new semantic meaning beyond the schema. The baseline of 3 is appropriate because the schema carries the burden.

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 clearly states the tool's verb and resource: 'Create a payment in YooKassa.' It also specifies the return of a confirmation URL and key capabilities (one-step/two-step, receipts, metadata). However, it does not differentiate from sibling tools like create_sbp_payment or create_recurring_payment, which is a minor gap.

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 description implies usage as a general payment creation tool by listing supported features, but it does not explicitly state when to use this tool versus specialized siblings like create_sbp_payment or create_split_payment. There are no exclusions or alternative recommendations, so usage is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theYahia/yookassa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server