Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

fund_growth

Retrieve growth data for investment funds by providing the fund code to analyze performance metrics and trends.

Instructions

获取基金增长数据

Args:
    fund_code: 基金代码

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fund_codeNoSZ000002

Implementation Reference

  • main.py:420-428 (handler)
    The main handler function for the 'fund_growth' tool. It is decorated with @mcp.tool() for registration, calls the pysnowball library's fund_growth method, processes the result with timestamps conversion, and returns the data.
    @mcp.tool()
def fund_growth(fund_code: str="SZ000002") -> dict:
    """获取基金增长数据
    
    Args:
        fund_code: 基金代码
    """
    result = ball.fund_growth(fund_code)
    return process_data(result)

Tool Definition Quality

C2.9/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 only states what data is retrieved ('基金增长数据') without mentioning any behavioral traits such as read-only status, potential rate limits, authentication needs, or what the output might look like. This is inadequate for a tool with no 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the main purpose, followed by a brief Args section. It avoids unnecessary verbosity, though the structure could be slightly improved by integrating the parameter info more seamlessly rather than as a separate section.

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?

Given the complexity (a data retrieval tool with no annotations, no output schema, and low schema coverage), the description is incomplete. It doesn't explain what 'fund growth data' entails, how it's returned, or any usage constraints, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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 description adds minimal parameter semantics by listing 'fund_code' in the Args section, but with 0% schema description coverage, it doesn't provide details like format, examples beyond the default, or constraints. Since there's only one parameter, the baseline is higher, but the description doesn't fully compensate for the lack of schema documentation.

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 as '获取基金增长数据' (get fund growth data), which is a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'fund_achievement', 'fund_asset', or 'fund_detail', which might also provide related fund data, so it doesn't reach the highest score.

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. With many sibling tools related to funds (e.g., fund_achievement, fund_asset), there's no indication of what makes 'fund_growth' unique or when it should be preferred over other fund-related tools.

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/liqiongyu/xueqiu_mcp'

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