Skip to main content
Glama
yop-platform

yop-mcp

by yop-platform
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

yeepay_yop_java_sdk_user_guide

Get the user guide for YOP Java SDK to integrate payment services with Yeepay's open platform. Access documentation and follow links for detailed implementation steps.

Instructions

通过此工具，获取易宝支付开放平台(YOP)的yop-java-sdk的使用说明，内容中包含链接时可以调用工具yeepay_yop_link_detail进一步获取其详细内容

Returns: str: 易宝支付开放平台(YOP)的yop-java-sdk的使用说明(markdown格式)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • yop_mcp/main.py:171-196 (handler)
    The handler function decorated with @mcp.tool() that implements the 'yeepay_yop_java_sdk_user_guide' tool. It dynamically fetches the platform version and downloads the Java SDK user guide content, falling back to a static URL if needed.
    @mcp.tool()
def yeepay_yop_java_sdk_user_guide() -> str:
    """
    通过此工具，获取易宝支付开放平台(YOP)的yop-java-sdk的使用说明，内容中包含链接时可以调用工具yeepay_yop_link_detail进一步获取其详细内容

    Returns:
        str: 易宝支付开放平台(YOP)的yop-java-sdk的使用说明(markdown格式)

    """
    try:
        platform_info = json.loads(
            HttpUtils.download_content(
                "https://open.yeepay.com/apis/commons/doc/platform/info"
            )
        )
        platform_version = platform_info.get("data").get("docVersion")
        return HttpUtils.download_content(
            "https://open.yeepay.com/apis/docs/platform/"
            + platform_version
            + "/sdk_guide/java-sdk-guide.html"
        )
    except (ValueError, TypeError, ConnectionError):
        return HttpUtils.download_content(
            "https://open.yeepay.com/docs-v3/platform/201.md"
        )

Tool Definition Quality

A3.5/5.0
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 behavioral disclosure. It mentions that the output is in markdown format and includes a note about linked content, but it doesn't cover important aspects like whether this is a read-only operation, potential rate limits, authentication requirements, or error handling. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 concise and front-loaded, stating the purpose in the first sentence and adding a useful note about linked content in the second. It avoids unnecessary details and is appropriately sized for a simple tool. However, the structure could be slightly improved by more clearly separating the purpose from usage guidelines.

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?

Given that the tool has no parameters, an output schema exists (implied by 'Returns: str'), and no annotations, the description is moderately complete. It explains what the tool does and provides a usage tip, but it lacks behavioral context (e.g., read-only nature, potential errors) that would be helpful for an AI agent. The output schema handles return values, so the description doesn't need to detail those.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter information, so it appropriately focuses on other aspects. Since there are no parameters, the baseline is 4, as the description doesn't have to compensate for any schema gaps.

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

Purpose4/5

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

The description clearly states the tool's purpose: '获取易宝支付开放平台(YOP)的yop-java-sdk的使用说明' (get usage instructions for the yop-java-sdk of YeePay's open platform). It specifies the resource (yop-java-sdk usage instructions) and the verb (get). However, it doesn't explicitly differentiate from sibling tools like 'yeepay_yop_sdk_and_tools_guide', which might cover similar SDK topics, leaving some 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 usage: it mentions that when links are present in the content, the tool 'yeepay_yop_link_detail' can be used to get further details. This gives a specific alternative tool for related actions. However, it doesn't explicitly state when to use this tool versus other siblings like 'yeepay_yop_sdk_and_tools_guide' or general overview tools, which could lead to confusion in tool selection.

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/yop-platform/yop-mcp'

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