Skip to main content
Glama
dontsovcmc

io.github.dontsovcmc/tochka-bank

by dontsovcmc

tochka_subscription_with_receipt

Create a subscription with a fiscal receipt. Provide customer code, amount, purpose, client email, and receipt items. Optionally enable recurring charges or save card.

Instructions

Create subscription with fiscal receipt.

For subscription without receipt, use tochka_subscription_create.

Args: customer_code: Customer code (9 chars, e.g. "100000001") amount: Subscription amount (> 0) purpose: Subscription purpose (1-140 chars) 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 (optional) recurring: Enable recurring charges (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
amountYes
purposeYes
recurringNo
save_cardNo
items_jsonYes
client_nameNo
consumer_idNo
merchant_idNo
client_emailYes
client_phoneNo
redirect_urlNo
customer_codeYes
payment_link_idNo
tax_system_codeNo
fail_redirect_urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations only include openWorldHint: true, meaning the tool may have dynamic behavior, but the description does not disclose any behavioral traits beyond basic operation. No mention of side effects, permissions, rate limits, or error states. The description offers minimal transparency beyond stating it creates a subscription.

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 well-structured: an opening sentence stating name and distinction, then a bullet-style list of parameters with constraints. Every item provides necessary information without redundancy.

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?

Given the complexity (15 parameters, 5 required, no schema descriptions), the description covers parameters thoroughly. It mentions redirect_url and fail_redirect_url, hinting at success/failure behavior. It does not explain the output, but an output schema exists, so that's acceptable. Some further context about the overall flow (e.g., payment link generation) would enhance completeness, but it is largely adequate.

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?

The input schema has 0% coverage, so the description carries the full burden of explaining parameters. It adds valuable constraints for each parameter, such as length limits for customer_code and purpose, positive amount, and optional fields with enums like tax_system_code. This greatly aids correct invocation.

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 the tool creates a subscription with a fiscal receipt, and explicitly distinguishes from the sibling tool 'tochka_subscription_create' for subscriptions without receipts. The verb 'create' and resource 'subscription with receipt' are specific.

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?

Explicitly tells when to use this tool (subscription with receipt) vs. alternative (tochka_subscription_create for without receipt). Does not provide broader usage context like prerequisites or when not to use, but the sibling reference is strong guidance.

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