robokassa-mcp

by artgas1

Overview Schema Source Related Servers Discussions Admin

Python

Remote

hold_cancel

Release reserved funds by canceling a payment hold without capturing the transaction.

Instructions

Release a hold without capturing the reserved funds.

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

Input Schema

Name	Required	Default
`inv_id`	Yes
`merchant_login`	No
`password1`	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

C2.9/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It mentions one key behavior (releasing without capturing), but omits important details like required authentication, whether the hold ID must be valid, what happens to associated funds, or any side effects. The output schema exists but is not described.

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 a single, concise sentence that directly states the tool's purpose. No extraneous information is included.

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

Completeness2/5

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

Given the tool's complexity (4 parameters, 1 required) and the presence of sibling tools for other hold operations, the description is too brief. It fails to cover prerequisites (e.g., hold must exist), state expectations, or error conditions. The output schema exists but is not referenced, leaving the agent without context on return value semantics.

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

Parameters1/5

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

Schema description coverage is 0%, meaning the description adds no information about parameters beyond the schema. The parameters (e.g., inv_id, merchant_login) are left unexplained, forcing the agent to infer their purpose from names alone. The description should at least indicate which parameters are important and how they relate to the cancellation.

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's function: 'Release a hold without capturing the reserved funds.' It uses a specific verb ('Release') and resource ('hold'), and the action is distinct from sibling tools like hold_init (create hold) and hold_confirm (capture hold).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives like hold_confirm or hold_cancel for other holds. It does not mention prerequisites, such as requiring an active hold, or scenarios where this tool should not be used.

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

Deploy Server