Skip to main content
Glama
24mlight

A-Share MCP Server

get_money_supply_data_year

Retrieve yearly money supply data for China's A-share market analysis. Specify date ranges to access historical monetary indicators for financial research and investment decisions.

Instructions

Yearly money supply data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNo
end_dateNo
limitNo
formatNomarkdown

Implementation Reference

  • The primary MCP tool handler for 'get_money_supply_data_year'. It is registered via @app.tool() decorator and executes the tool logic by delegating to the use case function with standardized error handling.
    @app.tool()
    def get_money_supply_data_year(start_date: Optional[str] = None, end_date: Optional[str] = None, limit: int = 250, format: str = "markdown") -> str:
        """Yearly money supply data."""
        return run_tool_with_handling(
            lambda: fetch_money_supply_data_year(
                active_data_source, start_date=start_date, end_date=end_date, limit=limit, format=format
            ),
            context="get_money_supply_data_year",
        )
  • mcp_server.py:55-55 (registration)
    Top-level registration call that invokes the function defining and registering the macroeconomic tools, including 'get_money_supply_data_year'.
    register_macroeconomic_tools(app, active_data_source)
  • Helper use case function that fetches yearly money supply data from the data source, applies validation, and formats the output as markdown or other specified format.
    def fetch_money_supply_data_year(data_source: FinancialDataSource, *, start_date: Optional[str], end_date: Optional[str], limit: int, format: str) -> str:
        validate_output_format(format)
        df = data_source.get_money_supply_data_year(start_date=start_date, end_date=end_date)
        meta = {"dataset": "money_supply_year", "start_date": start_date, "end_date": end_date}
        return format_table_output(df, format=format, max_rows=limit, meta=meta)
  • Abstract method in the FinancialDataSource interface defining the expected input parameters and return type for fetching money supply data.
    @abstractmethod
    def get_money_supply_data_year(self, start_date: Optional[str] = None, end_date: Optional[str] = None) -> pd.DataFrame:
        """Fetches yearly money supply data (M0, M1, M2 - year end balance)."""
        pass
  • Concrete implementation of the data source method using Baostock's query_money_supply_data_year API wrapped in a generic macro data fetcher.
    def get_money_supply_data_year(self, start_date: Optional[str] = None, end_date: Optional[str] = None) -> pd.DataFrame:
        """Fetches yearly money supply data (M0, M1, M2 - year end balance) using Baostock."""
        # Baostock expects YYYY format for dates here
        return _fetch_macro_data(bs.query_money_supply_data_year, "Yearly Money Supply", start_date, end_date)
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. 'Yearly money supply data' reveals nothing about whether this is a read operation, its safety, rate limits, authentication needs, or output format. It fails to describe any behavioral traits beyond the minimal purpose, leaving critical operational details unspecified.

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 extremely concise with just three words, making it front-loaded and free of unnecessary details. However, this conciseness borders on under-specification, but per the rubric, it scores high for brevity and structure without wasted words.

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 (a data retrieval tool with 4 parameters), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't cover parameter usage, behavioral aspects, or output expectations, making it insufficient for effective tool invocation by an AI agent.

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?

The description adds no meaning beyond the input schema, which has 0% description coverage for its 4 parameters (start_date, end_date, limit, format). It doesn't explain what these parameters do, their expected formats (e.g., date strings in YYYY-MM-DD), or default behaviors. With low schema coverage and no compensation in the description, this is inadequate.

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

Purpose3/5

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

The description 'Yearly money supply data' states what the tool provides but is vague about the action. It mentions the resource ('money supply data') and temporal scope ('yearly'), but doesn't specify a verb like 'retrieve', 'fetch', or 'list'. It distinguishes from sibling 'get_money_supply_data_month' by indicating yearly vs monthly data, but lacks clarity on the exact operation.

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 prerequisites, context for usage, or comparisons to sibling tools like 'get_money_supply_data_month' for monthly data or other financial data tools. Users must infer usage from the name and parameters 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/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