Skip to main content
Glama
al-one

MCP Server for stock and crypto

A股龙虎榜统计

stock_lhb_ggtj_sina

Retrieve statistical data for stocks appearing on China A-share market's Dragon Tiger List, showing institutional trading activity over specified periods.

Instructions

获取中国A股市场(上证、深证)的龙虎榜个股上榜统计数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo统计最近天数,仅支持: [5/10/30/60]5
limitNo返回数量(int,30-100)

Implementation Reference

  • The handler function decorated with @mcp.tool() implements the 'stock_lhb_ggtj_sina' tool. It fetches A-share dragon and tiger list (LHB) statistics data using akshare's ak.stock_lhb_ggtj_sina function wrapped in ak_cache for the specified number of days, limits the results, and returns as CSV.
    @mcp.tool(
        title="A股龙虎榜统计",
        description="获取中国A股市场(上证、深证)的龙虎榜个股上榜统计数据",
    )
    def stock_lhb_ggtj_sina(
        days: str = Field("5", description="统计最近天数,仅支持: [5/10/30/60]"),
        limit: int = Field(50, description="返回数量(int,30-100)", strict=False),
    ):
        dfs = ak_cache(ak.stock_lhb_ggtj_sina, symbol=days, ttl=3600)
        dfs = dfs.head(int(limit))
        return dfs.to_csv(index=False, float_format="%.2f").strip()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what data is retrieved but doesn't mention whether this is a read-only operation, potential rate limits, authentication requirements, data freshness, or error conditions. The description is purely functional without behavioral context needed for safe invocation.

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 Chinese sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a data retrieval tool and front-loads the essential information. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter data retrieval tool with no output schema and no annotations, the description adequately states what data is retrieved but lacks important context. It doesn't explain the return format, data structure, or what 'dragon-tiger board statistics' actually contain. The description is minimally viable but leaves significant gaps for the agent to understand what to expect.

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?

Schema description coverage is 100%, with both parameters ('days' and 'limit') well-documented in the schema. The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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: '获取中国A股市场(上证、深证)的龙虎榜个股上榜统计数据' (Get A-share market dragon-tiger board individual stock listing statistics). It specifies the resource (A-share market dragon-tiger board statistics) and action (get/retrieve). However, it doesn't explicitly differentiate from sibling tools like 'stock_indicators_a' or 'stock_sector_fund_flow_rank', which prevents a perfect 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. It doesn't mention what makes dragon-tiger board statistics unique compared to other stock data tools in the sibling list, nor does it specify prerequisites or exclusions. The agent must infer usage context from the tool 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/al-one/mcp-aktools'

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