Skip to main content
Glama
dontsovcmc

io.github.dontsovcmc/tochka-bank

by dontsovcmc

tochka_acquiring_payment_with_receipt

Create acquiring payment with fiscal receipt by specifying customer code, amount, purpose, payment modes, client email, and receipt items. Sends receipt to client email.

Instructions

Create acquiring payment operation with fiscal receipt.

For payment without receipt, use tochka_acquiring_payment_create.

Args: customer_code: Customer code (9 chars, e.g. "100000001") amount: Payment amount (> 0) purpose: Payment purpose (1-140 chars) payment_mode: Allowed payment methods, e.g. ["sbp", "card"] client_email: Receipt recipient email items_json: JSON array of receipt items [{name, amount, quantity, vatType?, paymentMethod?, paymentObject?}] redirect_url: Success redirect URL (optional) fail_redirect_url: Failure redirect URL (optional) save_card: Save card for future payments (optional) consumer_id: Consumer identifier (optional) merchant_id: Merchant identifier, 15 chars (optional) pre_authorization: Two-stage payment mode (optional) ttl: Link lifetime in minutes, 1-44640, default 10080 (optional) payment_link_id: Custom payment link ID, 1-45 chars (optional) client_name: Receipt recipient name (optional) client_phone: Receipt recipient phone (optional) tax_system_code: Tax system: osn, usn_income, usn_income_outcome, esn, patent (optional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttlNo
amountYes
purposeYes
save_cardNo
items_jsonYes
client_nameNo
consumer_idNo
merchant_idNo
client_emailYes
client_phoneNo
payment_modeYes
redirect_urlNo
customer_codeYes
payment_link_idNo
tax_system_codeNo
fail_redirect_urlNo
pre_authorizationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations only have openWorldHint. Description adds parameter constraints (e.g., ttl range, customer_code format) but does not disclose behavioral traits like idempotency, error handling, or authentication requirements beyond the implied creation action.

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?

Structured with purpose, sibling reference, and an 'Args' section listing parameters. Concise given the number of parameters, though could optionally be more tabular.

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?

Covers all parameters and sibling distinction. Lacks description of output/return value and prerequisites (e.g., merchant existence), but overall adequate for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates with detailed explanations for all 17 parameters, including formats, examples, and defaults.

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 clearly states 'Create acquiring payment operation with fiscal receipt' and explicitly distinguishes from the sibling 'tochka_acquiring_payment_create' for payments without receipt.

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?

Provides explicit alternative: 'For payment without receipt, use tochka_acquiring_payment_create.' Though other related tools exist, this single contrast is clear.

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/dontsovcmc/mcp-server-tochka-bank'

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