robokassa-mcp

by artgas1

Overview Schema Source Related Servers Discussions Admin

Python

Remote

hold_confirm

Capture reserved funds for a held transaction. Reduce the cart total before capture without increasing it.

Instructions

Capture previously-reserved funds for a held transaction.

Cart can be reduced (smaller receipt_items) before capture, but not increased. Pass the same OutSum (possibly smaller) as the original hold.

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": {
      "out_sum": "<out_sum>",
      "inv_id": "<inv_id>"
    },
    "name": "hold_confirm"
  }
}

Input Schema

Name	Required	Default
`out_sum`	Yes
`inv_id`	Yes
`merchant_login`	No
`password1`	No
`receipt_items`	No
`receipt_sno`	No
`algorithm`	No	md5

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Discloses important behavioral traits (cart reduction allowed, OutSum can be smaller) and the fundamental action of capturing, but lacks details on auth needs, rate limits, or failure behavior.

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?

Two sentences plus a line break; every word is necessary and efficiently conveys critical information without verbosity.

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

Completeness3/5

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

Adequate for a tool with an output schema, but missing explanation of required inv_id and other optional parameters; relies on domain knowledge.

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

Parameters2/5

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

Provides context for two parameters (out_sum and receipt_items) but leaves five others (including required inv_id) unexplained, despite 0% schema description coverage.

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 uses specific verb 'Capture' and resource 'previously-reserved funds for a held transaction', clearly distinguishing from siblings like hold_init and hold_cancel.

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?

Clearly states when to use (to capture a held transaction) and includes constraints (cart can be reduced, pass same OutSum), but does not explicitly mention when not to use or compare to alternatives.

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

Deploy Server