yeepay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_webpage_yeepay_paymentC | 创建移动支付订单工具 |
| query_yeepay_payment_statusC | 查询支付状态工具 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one creates a payment order, and the other queries the payment status. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent verb_noun pattern with underscores: 'create_webpage_yeepay_payment' and 'query_yeepay_payment_status'. The naming is predictable and readable, with no deviations in style or convention.
With only two tools, the server feels thin for a payment processing domain. While the tools cover creation and status querying, typical payment workflows might require additional operations like refunds, cancellations, or listing transactions, making the tool count insufficient for comprehensive coverage.
The tool set is severely incomplete for a payment processing server. It lacks essential operations such as refunding payments, canceling orders, handling webhooks, or retrieving transaction lists. This creates significant gaps that could lead to agent failures when attempting full payment lifecycle management.