Skip to main content
Glama
24mlight

A-Share MCP Server

list_industries

Retrieve distinct industry classifications for China's A-share market on a specific date to analyze sector composition and market structure.

Instructions

List distinct industries for a given date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
formatNomarkdown

Implementation Reference

  • The MCP tool handler for 'list_industries'. Decorated with @app.tool() for automatic registration and schema inference. Logs the invocation and delegates to the core use case logic via run_tool_with_handling.
    @app.tool()
    def list_industries(date: Optional[str] = None, format: str = "markdown") -> str:
        """List distinct industries for a given date."""
        logger.info("Tool 'list_industries' called date=%s", date or "latest")
        return run_tool_with_handling(
            lambda: fetch_list_industries(active_data_source, date=date, format=format),
            context="list_industries",
        )
  • Core implementation logic for listing industries: fetches all stock industry data, extracts unique sorted industries, and formats as markdown table.
    def fetch_list_industries(data_source: FinancialDataSource, *, date: Optional[str], format: str) -> str:
        validate_output_format(format)
        df = data_source.get_stock_industry(code=None, date=date)
        if df is None or df.empty:
            return "(No data available to display)"
        col = "industry" if "industry" in df.columns else df.columns[-1]
        out = df[[col]].drop_duplicates().sort_values(by=col)
        out = out.rename(columns={col: "industry"})
        meta = {"as_of": date or "latest", "count": int(out.shape[0])}
        return format_table_output(out, format=format, max_rows=out.shape[0], meta=meta)
  • mcp_server.py:53-53 (registration)
    Top-level call to register_index_tools, which includes the registration of the 'list_industries' handler via its @app.tool() decorator.
    register_index_tools(app, active_data_source)
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 states the action ('List') but doesn't describe output format, pagination, rate limits, authentication needs, or what happens if the date is null. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 sentence that is front-loaded with the core action and constraint. There is no wasted text, and it directly communicates the essential information without unnecessary elaboration.

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 the complexity (2 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain return values, parameter details, or behavioral traits, leaving the agent with insufficient context to use the tool effectively beyond a basic understanding of its purpose.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only mentions the 'date' parameter implicitly ('for a given date') and ignores the 'format' parameter entirely. This adds minimal meaning beyond the schema, failing to address the coverage gap adequately.

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 verb ('List') and resource ('distinct industries') with a specific constraint ('for a given date'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_industry_members' or 'get_stock_industry', which appear related but have different functions.

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 like 'get_industry_members' or 'get_stock_industry', nor does it mention prerequisites, exclusions, or specific contexts. Usage is implied only by the date parameter, but without sibling differentiation.

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