Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

capital_assort

Retrieve capital transaction distribution data for specific stocks to analyze trading patterns and investor behavior.

Instructions

获取资金成交分布数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stock_codeNoSZ000002

Implementation Reference

  • main.py:120-124 (handler)
    The MCP tool handler for 'capital_assort'. Registered via @mcp.tool() decorator. Takes stock_code parameter, fetches data using pysnowball.ball.capital_assort, processes timestamps with process_data, and returns as dict. The function signature provides input schema.
    @mcp.tool()
def capital_assort(stock_code: str="SZ000002") -> dict:
    """获取资金成交分布数据"""
    result = ball.capital_assort(stock_code)
    return process_data(result)

Tool Definition Quality

C2.6/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 full burden. It states it 'gets' data, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, data freshness, or what 'distribution' means (e.g., time-based, volume-based). For a tool with no annotation coverage, 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.

Conciseness5/5

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

The description is a single, efficient phrase in Chinese that directly states the tool's function. It's front-loaded with no wasted words, making it easy to parse quickly. However, this conciseness comes at the cost of detail, which is reflected in other scores.

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 no annotations, 0% schema description coverage, no output schema, and one parameter, the description is incomplete. It doesn't explain what 'capital transaction distribution data' includes, how the parameter influences results, or what the return format is. For a tool with such minimal structured data, the description should provide more context to be useful.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions no parameters at all, while the input schema has one parameter ('stock_code'). The description doesn't add any meaning about what 'stock_code' represents or how it affects the output. With low coverage and no parameter info in the description, it fails to provide necessary context.

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 '获取资金成交分布数据' (Get capital transaction distribution data) states a general purpose but lacks specificity about what 'capital transaction distribution' entails or what resource it operates on. It distinguishes from siblings like 'capital_flow' or 'capital_history' only by the term 'distribution', but doesn't clarify how it differs functionally. The purpose is vague rather than specific.

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?

No guidance is provided on when to use this tool versus alternatives like 'capital_flow' or 'capital_history'. The description implies it's for capital-related data but doesn't specify contexts, prerequisites, or exclusions. Without any usage instructions, the agent must infer from the name alone.

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