Skip to main content
Glama

yeepay_yop_sdk_and_tools_guide

Access usage guides for Yeepay Open Platform SDKs and tools, including integration best practices.

Instructions

通过此工具,获取易宝支付开放平台(YOP)提供的各种SDK和工具的使用说明,内容中包含链接时可以调用工具yeepay_yop_link_detail进一步获取其详细内容

Returns: str: 易宝支付开放平台(YOP)提供的各种SDK和工具的使用说明,以及对接最佳实践等(markdown格式)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for yeepay_yop_sdk_and_tools_guide. It is decorated with @mcp.tool() and downloads SDK/tools documentation from https://open.yeepay.com/docs-v3/platform/llms.txt using HttpUtils.download_content.
    @mcp.tool()
    def yeepay_yop_sdk_and_tools_guide() -> str:
        """
        通过此工具,获取易宝支付开放平台(YOP)提供的各种SDK和工具的使用说明,内容中包含链接时可以调用工具yeepay_yop_link_detail进一步获取其详细内容
    
        Returns:
            str: 易宝支付开放平台(YOP)提供的各种SDK和工具的使用说明,以及对接最佳实践等(markdown格式)
    
        """
        try:
            return HttpUtils.download_content(
                "https://open.yeepay.com/docs-v3/platform/llms.txt"
            )
        except (ValueError, TypeError, ConnectionError):
            return "HTTP请求失败, url: https://open.yeepay.com/docs-v3/platform/llms.txt"
  • The tool is registered with the MCP server via the @mcp.tool() decorator on the handler function.
    @mcp.tool()
    def yeepay_yop_sdk_and_tools_guide() -> str:
  • HttpUtils.download_content is the helper that performs the actual HTTP GET request to download content from a URL. It uses httpx with HTTP/2 support.
    @staticmethod
    def download_content(url: str, timeout: Optional[int] = None) -> str:
        """
        同步下载文件(无进度显示)并返回文件内容
    
        Args:
            url: 下载地址
            timeout: 超时时间(秒)
    
        Returns:
            str: 下载的文本内容
        """
        try:
            with httpx.Client(http2=True, timeout=timeout) as client:  # 启用HTTP/2加速
                response = client.get(url)
                response.raise_for_status()  # 自动检测4xx/5xx错误
                content = response.text
            print(f"已获取内容,长度: {len(content)} 字符")
            return content
        except httpx.HTTPStatusError as e:
            print(f"HTTP错误 {e.response.status_code}")
            return f"HTTP请求失败: HTTP {e.response.status_code}"
        except Exception as e:  # 保持通用异常处理以支持测试
            print(f"请求失败:{str(e)}")
            return f"HTTP请求失败: {str(e)}"
  • Import of HttpUtils from tools.http_utils and creation of the FastMCP server instance named 'yop-mcp'.
    from tools.http_utils import HttpUtils
    
    # Create an MCP server
    mcp = FastMCP("yop-mcp")
    
    
    @mcp.tool()
    def yeepay_yop_overview() -> str:
        """
        通过此工具,可以了解易宝支付开放平台(YOP)的平台规范,接入流程,网站地图,内容中包含链接时可以调用工具yeepay_yop_link_detail进一步获取其详细内容
    
        Returns:
            str: 易宝支付开放平台(YOP)的概览信息(markdown格式)
        """
    
        return HttpUtils.download_content("https://open.yeepay.com/docs-v3/llms.txt")
Behavior4/5

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

No annotations provided, so the description carries the burden. It discloses that the tool retrieves instructions and may include links, but no further behavioral details (e.g., no destructive actions). This is adequate for a simple retrieval tool.

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 two sentences, front-loading the purpose and a usage hint. Every sentence is necessary and concise.

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?

Given zero parameters and a simple return value (markdown string), the description is sufficient. It also mentions a related tool, enhancing completeness for agents.

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?

There are zero parameters, so baseline is 4. The description does not need to add parameter meaning as there are none.

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 provides usage instructions for SDKs and tools from Yeepay Open Platform. It distinguishes itself by mentioning when to use a sibling tool for links.

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 gives explicit guidance on using yeepay_yop_link_detail for detailed content, implying this tool is for initial instructions. However, it does not specify when to prefer this over other sibling tools like yeepay_yop_api_detail.

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