Skip to main content
Glama
24mlight

A Share MCP

by 24mlight

get_performance_express_report

Generate performance reports for A-share stocks within specified date ranges to analyze financial data and market indicators.

Instructions

Performance express report within date range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
start_dateYes
end_dateYes
limitNo
formatNomarkdown

Implementation Reference

  • MCP tool handler for get_performance_express_report. Decorated with @app.tool(), validates inputs via run_tool_with_handling, delegates to use case fetch_performance_express_report.
    @app.tool()
    def get_performance_express_report(code: str, start_date: str, end_date: str, limit: int = 250, format: str = "markdown") -> str:
        """Performance express report within date range."""
        return run_tool_with_handling(
            lambda: fetch_performance_express_report(
                active_data_source, code=code, start_date=start_date, end_date=end_date, limit=limit, format=format
            ),
            context=f"get_performance_express_report:{code}:{start_date}-{end_date}",
        )
  • mcp_server.py:52-52 (registration)
    Registration call for financial reports tools, including get_performance_express_report, in the main MCP server setup.
    register_financial_report_tools(app, active_data_source)
  • Use case helper that fetches data from FinancialDataSource interface, applies formatting and validation.
    def fetch_performance_express_report(data_source: FinancialDataSource, *, code: str, start_date: str, end_date: str, limit: int, format: str) -> str:
        validate_output_format(format)
        df = data_source.get_performance_express_report(code=code, start_date=start_date, end_date=end_date)
        meta = {"code": code, "start_date": start_date, "end_date": end_date, "dataset": "Performance Express"}
        return format_table_output(df, format=format, max_rows=limit, meta=meta)
  • Abstract method definition in FinancialDataSource interface, defining the expected input/output signature for the core data fetching method.
    @abstractmethod
    def get_performance_express_report(self, code: str, start_date: str, end_date: str) -> pd.DataFrame:
        pass
  • Concrete implementation in BaostockDataSource using bs.query_performance_express_report to fetch raw data from Baostock API.
    def get_performance_express_report(self, code: str, start_date: str, end_date: str) -> pd.DataFrame:
        """Fetches performance express reports (业绩快报) using Baostock."""
        logger.info(
            f"Fetching Performance Express Report for {code} ({start_date} to {end_date})")
        try:
            with baostock_login_context():
                rs = bs.query_performance_express_report(
                    code=code, start_date=start_date, end_date=end_date)
    
                if rs.error_code != '0':
                    logger.error(
                        f"Baostock API error (Perf Express) for {code}: {rs.error_msg} (code: {rs.error_code})")
                    if "no record found" in rs.error_msg.lower() or rs.error_code == '10002':
                        raise NoDataFoundError(
                            f"No performance express report found for {code} in range {start_date}-{end_date}. Baostock msg: {rs.error_msg}")
                    else:
                        raise DataSourceError(
                            f"Baostock API error fetching performance express report: {rs.error_msg} (code: {rs.error_code})")
    
                data_list = []
                while rs.next():
                    data_list.append(rs.get_row_data())
    
                if not data_list:
                    logger.warning(
                        f"No performance express report found for {code} in range {start_date}-{end_date} (empty result set).")
                    raise NoDataFoundError(
                        f"No performance express report found for {code} in range {start_date}-{end_date} (empty result set).")
    
                result_df = pd.DataFrame(data_list, columns=rs.fields)
                logger.info(
                    f"Retrieved {len(result_df)} performance express report records for {code}.")
                return result_df
    
        except (LoginError, NoDataFoundError, DataSourceError, ValueError) as e:
            logger.warning(
                f"Caught known error fetching performance express report for {code}: {type(e).__name__}")
            raise e
        except Exception as e:
            logger.exception(
                f"Unexpected error fetching performance express report for {code}: {e}")
            raise DataSourceError(
                f"Unexpected error fetching performance express report for {code}: {e}")
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions nothing about whether this is a read-only operation, potential rate limits, authentication needs, data freshness, or what the output looks like (e.g., report format, structure). For a tool with 5 parameters and no output schema, 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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, though overly brief. While concise, it sacrifices necessary detail for brevity.

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 complexity (5 parameters, 3 required, 0% schema coverage, no annotations, no output schema, many sibling tools), the description is completely inadequate. It doesn't explain what the tool returns, how to interpret parameters, behavioral constraints, or differentiation from alternatives. This leaves critical gaps for effective tool use.

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 adds no information about parameters beyond implying a date range (start_date, end_date). It doesn't explain 'code' (stock code? index?), 'limit' (pagination? max rows?), or 'format' (output format options). With low coverage, the description fails to compensate.

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 'Performance express report within date range' restates the tool name 'get_performance_express_report' with minimal elaboration. It mentions 'report' and 'date range' but doesn't specify what type of performance data, for which entities (stocks, indices, etc.), or what distinguishes it from sibling tools like get_profit_data or get_operation_data. This is essentially a tautological expansion of the name.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for financial data (e.g., get_profit_data, get_balance_data, get_historical_k_data), the description offers no context about appropriate use cases, prerequisites, or comparisons. This leaves the agent guessing about 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/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