Skip to main content
Glama
24mlight

A-Share MCP Server

get_dupont_data

Retrieve quarterly DuPont analysis data for A-share stocks to assess financial performance through return on equity decomposition.

Instructions

Quarterly Dupont analysis data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
yearYes
quarterYes
limitNo
formatNomarkdown

Implementation Reference

  • The primary MCP tool handler for 'get_dupont_data', decorated with @app.tool(). It invokes the fetch_dupont_data use case wrapped in error handling and logging.
    @app.tool()
    def get_dupont_data(code: str, year: str, quarter: int, limit: int = 250, format: str = "markdown") -> str:
        """Quarterly Dupont analysis data."""
        return run_tool_with_handling(
            lambda: fetch_dupont_data(active_data_source, code=code, year=year, quarter=quarter, limit=limit, format=format),
            context=f"get_dupont_data:{code}:{year}Q{quarter}",
        )
  • mcp_server.py:52-52 (registration)
    Invocation of the registration function that registers the financial_reports tools, including get_dupont_data, to the FastMCP app.
    register_financial_report_tools(app, active_data_source)
  • Use case helper that performs input validation, fetches raw DuPont data from the data source, and formats it for output.
    def fetch_dupont_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_dupont_data(code=code, year=year, quarter=quarter)
        return _format_financial_df(df, code=code, year=year, quarter=quarter, dataset="Dupont", format=format, limit=limit)
  • Concrete implementation in BaostockDataSource that calls the Baostock query_dupont_data API via a shared financial data fetcher.
    def get_dupont_data(self, code: str, year: str, quarter: int) -> pd.DataFrame:
        """Fetches quarterly DuPont analysis data using Baostock."""
        return _fetch_financial_data(bs.query_dupont_data, "DuPont Analysis", code, year, quarter)
  • Abstract method definition in the FinancialDataSource interface, defining the contract for DuPont data retrieval.
    @abstractmethod
    def get_dupont_data(self, code: str, year: str, quarter: int) -> pd.DataFrame:
        pass
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to do so: it doesn't indicate if this is a read-only operation, whether it requires authentication, potential rate limits, or what the output looks like (e.g., data format, structure). The description is too vague to inform the agent about how the tool behaves beyond its basic purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is concise with a single phrase, but it's under-specified rather than efficiently informative. It's front-loaded but lacks necessary detail, making it more of a placeholder than a helpful summary. While not verbose, it fails to earn its place by omitting critical information.

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, no annotations, no output schema), the description is severely incomplete. It doesn't cover tool behavior, parameter meanings, output expectations, or usage context. For a data retrieval tool with multiple inputs, this minimal description is inadequate to guide an AI agent effectively.

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 (code, year, quarter, limit, format) are documented in the schema. The description adds no information about these parameters—it doesn't explain what 'code' refers to (e.g., stock code, index), the expected format for 'year' and 'quarter', or the purpose of 'limit' and 'format'. This leaves all parameters semantically undefined.

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 Dupont analysis data' restates the tool name 'get_dupont_data' in slightly different wording, making it tautological. It doesn't specify what action the tool performs (e.g., 'retrieve', 'fetch', or 'calculate') or clarify what 'Dupont analysis data' entails, beyond implying it's quarterly. Compared to siblings like 'get_balance_data' or 'get_cash_flow_data', it lacks distinctiveness in purpose.

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. It doesn't mention any prerequisites, context for use, or comparisons to sibling tools (e.g., 'get_fina_indicator' or 'get_profit_data'), leaving the agent with no usage instructions.

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