Skip to main content
Glama
Sign In
yeepay-mcp

yeepay-mcp

by yop-platform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_webpage_yeepay_payment

Generate a webpage payment order for Yeepay by providing merchant order ID, transaction amount, and product details. Integrates with Yeepay services via the MCP protocol.

Instructions

创建移动支付订单工具

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": {
      "orderId": "<orderId>",
      "amount": "<amount>",
      "goodsName": "<goodsName>"
    },
    "name": "create_webpage_yeepay_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes交易金额
goodsNameYes商品名称
orderIdYes商户订单号
userIpNo用户IP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states '创建' (create) which implies a write/mutation operation, but doesn't disclose any behavioral traits like authentication requirements, rate limits, whether the operation is idempotent, what happens on failure, or what the expected response looks like. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise - a single phrase that directly states the tool's purpose. There's zero waste or unnecessary verbiage, and it's appropriately sized for what it communicates.

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?

For a payment creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, or important behavioral aspects. Given the complexity of payment processing and the lack of structured metadata, the description should provide more complete context about the operation.

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

Parameters3/5

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

The schema description coverage is 100%, with all parameters clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '创建移动支付订单工具' translates to 'Create mobile payment order tool', which clearly states the action (create) and resource (mobile payment order). However, it doesn't distinguish from its sibling 'query_yeepay_payment_status' beyond the basic verb difference, and the purpose could be more specific about what type of payment order is being created.

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 guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when-not-to-use scenarios, or how it relates to the sibling tool 'query_yeepay_payment_status' for checking payment status after creation.

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

Deploy Server

Other Tools

Related Tools