Skip to main content
Glama
alipay

AlipayPlus MCP Server

Official
by alipay

create_refund

Initiate full or partial refunds for successful payments. Specify the original payment request ID, refund request ID, amount, and currency to process refunds.

Instructions

The tool is used by the Acquiring Service Provider (ACQP) to initiate a refund of a successful payment.The refund can be full or partial. A transaction can have multiple refunds as long as the total refund amount is less than or equal to the original transaction amount.

    Args:
        payment_request_id: The request ID of the payment to be refunded, assigned by the ACQP to identify the original payment order.Maximum length: 64 characters
        refund_request_id: The unique ID that is assigned by the ACQP to identify a refund request. Maximum length: 64 characters.
        refund_amount_value: The amount to charge as a positive integer in the smallest currency unit. (That is, 100 cents to charge $1.00, or 100 to charge JPY 100, a 0-decimal currency).Value range: 1 - unlimited
        refund_currency: The currency code of the amount. The value of this parameter must be an alphabetic code that follows the ISO 4217 standard, for example, "EUR" for Euros.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refund_currencyYes
refund_request_idYes
payment_request_idYes
refund_amount_valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains key behavior: refunds can be full or partial, multiple refunds are allowed, and total refunds cannot exceed the original amount. However, it omits details like authorization requirements, error conditions, or reversibility, leaving gaps in transparency.

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?

The description is well-structured: a concise overview of purpose and behavior followed by a clear Args list. It is slightly verbose due to parameter details, but every sentence adds value, and the structure aids scanning.

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?

For a tool with 4 required parameters and no enums or nesting, the description covers the core semantics and business rules. An output schema exists, so return values need not be described. Minor gaps remain (e.g., error handling), but the description is largely complete.

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 description includes a detailed Args section that explains every parameter: purpose, assignment, maximum length, value ranges, and currency standard. Since schema coverage is 0%, this fully compensates and adds significant meaning beyond the bare property titles.

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: 'initiate a refund of a successful payment.' It names the actor (ACQP), the resource (payment refund), and the action (initiate), distinguishing it from siblings like create_payment and cancel_payment. No ambiguity.

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?

The description provides clear context for when to use the tool: it is for refunds of successful payments, and it specifies constraints (full or partial, total refunds <= original amount). It does not explicitly mention alternatives or exclusions, but the context is sufficient to infer appropriate usage.

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/alipay/global-alipayplus-mcp'

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