Skip to main content
Glama
24mlight

A-Share MCP Server

get_growth_data

Retrieve quarterly growth capability data for A-share stocks to analyze financial performance trends and investment potential.

Instructions

Quarterly growth capability data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
yearYes
quarterYes
limitNo
formatNomarkdown

Implementation Reference

  • The primary handler for the 'get_growth_data' MCP tool. This @app.tool()-decorated function implements the tool logic by delegating to the fetch_growth_data use case with error handling.
    @app.tool()
    def get_growth_data(code: str, year: str, quarter: int, limit: int = 250, format: str = "markdown") -> str:
        """Quarterly growth capability data."""
        return run_tool_with_handling(
            lambda: fetch_growth_data(active_data_source, code=code, year=year, quarter=quarter, limit=limit, format=format),
            context=f"get_growth_data:{code}:{year}Q{quarter}",
        )
  • mcp_server.py:52-52 (registration)
    Invocation of register_financial_report_tools during server startup, which registers the get_growth_data tool (and other financial report tools) with the FastMCP app.
    register_financial_report_tools(app, active_data_source)
  • Helper use case function called by the tool handler. Performs input validation, fetches raw growth data from the data source, and formats the output as markdown table.
    def fetch_growth_data(data_source: FinancialDataSource, *, code: str, year: str, quarter: int, limit: int, format: str) -> str:
        validate_year(year)
        validate_quarter(quarter)
        validate_output_format(format)
        df = data_source.get_growth_data(code=code, year=year, quarter=quarter)
        return _format_financial_df(df, code=code, year=year, quarter=quarter, dataset="Growth", format=format, limit=limit)
  • Input schema defined by function signature and docstring for the MCP tool.
    def get_growth_data(code: str, year: str, quarter: int, limit: int = 250, format: str = "markdown") -> str:
        """Quarterly growth capability data."""
        return run_tool_with_handling(
            lambda: fetch_growth_data(active_data_source, code=code, year=year, quarter=quarter, limit=limit, format=format),
            context=f"get_growth_data:{code}:{year}Q{quarter}",
        )
Behavior1/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. The description reveals nothing about whether this is a read-only operation, whether it requires authentication, what format the data returns in, whether there are rate limits, or what happens when parameters are invalid. For a data retrieval tool with 5 parameters, this lack of behavioral context is a significant gap.

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 extremely concise - a single three-word phrase. While this is efficient and front-loaded, it's arguably too brief given the tool's complexity (5 parameters, no annotations, no output schema). The conciseness comes at the expense of clarity and completeness.

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

Completeness1/5

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

Given the tool's complexity (5 parameters, 3 required), complete lack of annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It provides no information about what the tool actually does, how to use it properly, what it returns, or how it differs from the many similar financial data tools on the server.

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

Parameters1/5

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

Schema description coverage is 0%, meaning none of the 5 parameters have descriptions in the schema. The tool description provides no information about what 'code', 'year', 'quarter', 'limit', or 'format' mean in this context. The description doesn't explain what type of code (stock code? industry code?), what year format, what quarter values are valid, what the limit applies to, or what format options exist beyond the default 'markdown'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Quarterly growth capability data' is tautological - it essentially restates the tool name 'get_growth_data' without specifying what action is performed. It doesn't clearly state whether this retrieves, calculates, analyzes, or generates growth data. While it mentions 'quarterly' which hints at time-based data, it lacks a specific verb and doesn't distinguish this tool from its many financial data siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 40+ sibling tools on the server (including get_balance_data, get_cash_flow_data, get_profit_data, etc.), there's no indication of what makes 'growth capability data' distinct or when an agent should choose this specific tool over other financial data retrieval 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/24mlight/a-share-mcp-is-just-i-need'

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