Skip to main content
Glama
liqiongyu

Xueqiu MCP

by liqiongyu

index_basic_info

Retrieve essential details for stock market indices using Xueqiu MCP. Provide an index code to access fundamental data for investment analysis.

Instructions

获取指数基本信息

Args:
    index_code: 指数代码

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
index_codeNoSZ000002

Implementation Reference

  • main.py:310-319 (handler)
    The main handler function for the 'index_basic_info' tool. It is decorated with @mcp.tool() for registration, takes an index_code parameter, calls ball.index_basic_info(index_code), processes the result with process_data, and returns it as a dict. The docstring provides the schema description.
    @mcp.tool()
    def index_basic_info(index_code: str="SZ000002") -> dict:
        """获取指数基本信息
        
        Args:
            index_code: 指数代码
        """
        result = ball.index_basic_info(index_code)
        return process_data(result)
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 the action ('获取') without detailing permissions, rate limits, output format, or error handling. For a tool with no annotation coverage, this is a significant gap in transparency.

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 with two sentences: one stating the purpose and another listing the parameter. It's front-loaded with the main action, though the Args section could be integrated more smoothly. No wasted words, but structure is basic.

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, and no output schema, the description is incomplete. It doesn't explain what 'basic information' includes, how to interpret results, or handle errors, making it inadequate for a tool with one parameter and unclear output.

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 description adds minimal semantics by listing 'index_code' in the Args section, but schema description coverage is 0%, so the schema provides no parameter details. With only one parameter and the description naming it, this partially compensates, though it doesn't explain format or constraints beyond the default in the schema.

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 states the purpose as '获取指数基本信息' (get index basic information), which is clear but vague. It specifies the verb '获取' (get) and resource '指数基本信息' (index basic information), but doesn't detail what constitutes 'basic information' or differentiate it from sibling tools like 'index_details_data' or 'index_perf_30'.

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. The description doesn't mention prerequisites, exclusions, or compare it to sibling tools like 'index_details_data' or 'index_perf_30', leaving the agent without context for 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/liqiongyu/xueqiu_mcp'

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