Skip to main content
Glama

yeepay_yop_product_overview

Retrieves a markdown overview of YeePay Open Platform's product capabilities, with links for further detail via a related tool.

Instructions

通过此工具,获取易宝支付开放平台(YOP)的产品能力概览,内容中包含链接时可以调用工具yeepay_yop_link_detail进一步获取其详细内容

Returns: str: 易宝支付开放平台(YOP)的产品能力概览(markdown格式)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'yeepay_yop_product_overview' tool. It is decorated with @mcp.tool() and calls HttpUtils.download_content() to fetch product overview content from 'https://open.yeepay.com/docs-v3/product/llms.txt'.
    @mcp.tool()
    def yeepay_yop_product_overview() -> str:
        """
        通过此工具,获取易宝支付开放平台(YOP)的产品能力概览,内容中包含链接时可以调用工具yeepay_yop_link_detail进一步获取其详细内容
    
        Returns:
            str: 易宝支付开放平台(YOP)的产品能力概览(markdown格式)
        """
    
        return HttpUtils.download_content(
            "https://open.yeepay.com/docs-v3/product/llms.txt"
        )
  • yop_mcp/main.py:26-26 (registration)
    The tool is registered via the @mcp.tool() decorator on FastMCP instance 'mcp' (created on line 11).
    @mcp.tool()
  • The HttpUtils.download_content() static method used by the handler to fetch the markdown content from the remote URL using httpx.
    @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)}"
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as authentication requirements, rate limits, or side effects. It only implies a read operation by saying 'get', but fails to provide explicit safety or dependency info.

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 a single sentence that front-loads the main purpose and immediately follows with an important usage note about the sibling tool. No words are wasted, and it is well-structured.

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?

For a parameterless tool with output described, the description covers the main use and linking behavior. However, it does not differentiate from the very similarly named sibling tool 'yeepay_yop_overview', which could cause confusion. Hence a slight deduction.

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?

There are no parameters, and schema coverage is 100%. The description adds some value by mentioning the output format (markdown) and linking behavior, but these are not parameter semantics. Following the baseline rule, a score of 3 is appropriate.

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 the tool retrieves an overview of YOP product capabilities, using a specific verb ('get') and resource. It also distinguishes itself by noting that when links appear in the output, the sibling tool yeepay_yop_link_detail should be used, which clarifies its scope.

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 explicit guidance on when to use this tool (to get an overview) and when to use an alternative (yeepay_yop_link_detail for details of links). However, it does not differentiate from the similarly named sibling tool 'yeepay_yop_overview', so it slightly lacks completeness in terms of when not to use this tool.

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