Skip to main content
Glama
alipay

AlipayPlus MCP Server

Official
by alipay

create_payment

Send order placement requests to Alipay+ as an Acquiring Service Provider. Specify payment request ID, order amount with currency and description to initiate a payment.

Instructions

The tool is used by the Acquiring Service Provider (ACQP) to send a request to Alipay+ to place orders.

    Args:
        payment_request_id: TThe unique ID assigned by a merchant to identify a payment request. Maximum length: 64 characters
        order_amount_currency: The transaction currency that is specified in the contract. A 3-letter currency code that follows the ISO 4217 standard.Maximum length: 3 characters
        order_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
        order_description: Summary description of the order, which is used for user consumption records display or other further actions.Maximum length: 256 characters
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_descriptionYes
order_amount_valueYes
payment_request_idYes
order_amount_currencyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states the action (sending a request to place orders) without mentioning side effects, error scenarios, idempotency, or whether the operation is synchronous. This is insufficient for a payment creation tool that likely has significant side effects.

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 opens with a clear purpose statement and follows with structured parameter documentation. It is appropriately sized for four parameters, with no wasted sentences. Minor issues like the typo 'TThe' and the slightly verbose example in order_amount_value slightly detract from an otherwise clean structure.

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?

The description covers the purpose and all parameters, and an output schema exists to explain return values. However, it lacks usage guidelines and deeper behavioral transparency, such as when to use this tool versus siblings or what side effects to expect. This makes it only partially complete for an agent to use it confidently.

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 Args section provides detailed semantics for all four parameters, including format constraints (ISO 4217, max lengths), value ranges, and examples (e.g., smallest currency unit). This fully compensates for the 0% schema description coverage, adding significant meaning beyond the plain parameter names.

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 that the tool sends a request to Alipay+ to place orders, specifying the actor (ACQP) and the resource (orders). This distinguishes it from sibling tools like query_payment and cancel_payment, which have different purposes.

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

Usage Guidelines3/5

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

The description implies usage for creating a payment order via Alipay+, but it does not explicitly state when to use this tool versus alternatives like query_payment or create_refund. No exclusions, prerequisites, or alternative tool references are provided, so the guidance is only implied.

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