Skip to main content
Glama
24mlight

A-Share MCP Server

get_deposit_rate_data

Retrieve benchmark deposit rate data for China's A-share market analysis, supporting date ranges and multiple output formats.

Instructions

Benchmark deposit rates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNo
end_dateNo
limitNo
formatNomarkdown

Implementation Reference

  • The main handler function for the 'get_deposit_rate_data' tool, decorated with @app.tool(), which handles execution by delegating to the use case via run_tool_with_handling.
    @app.tool()
    def get_deposit_rate_data(start_date: Optional[str] = None, end_date: Optional[str] = None, limit: int = 250, format: str = "markdown") -> str:
        """Benchmark deposit rates."""
        return run_tool_with_handling(
            lambda: fetch_deposit_rate_data(active_data_source, start_date=start_date, end_date=end_date, limit=limit, format=format),
            context="get_deposit_rate_data",
        )
  • Abstract method definition in FinancialDataSource interface, specifying the expected signature for concrete data source implementations of get_deposit_rate_data.
    @abstractmethod
    def get_deposit_rate_data(self, start_date: Optional[str] = None, end_date: Optional[str] = None) -> pd.DataFrame:
        """Fetches benchmark deposit rates."""
        pass
  • mcp_server.py:55-55 (registration)
    Invocation of register_macroeconomic_tools during server startup, which defines and registers the get_deposit_rate_data tool among others.
    register_macroeconomic_tools(app, active_data_source)
  • Use case function called by the tool handler; fetches raw data from data source, validates output format, adds metadata, and formats as table.
    def fetch_deposit_rate_data(data_source: FinancialDataSource, *, start_date: Optional[str], end_date: Optional[str], limit: int, format: str) -> str:
        validate_output_format(format)
        df = data_source.get_deposit_rate_data(start_date=start_date, end_date=end_date)
        meta = {"dataset": "deposit_rate", "start_date": start_date, "end_date": end_date}
        return format_table_output(df, format=format, max_rows=limit, meta=meta)
  • Concrete implementation in BaostockDataSource that delegates to shared _fetch_macro_data helper for querying the Baostock deposit rate API.
    def get_deposit_rate_data(self, start_date: Optional[str] = None, end_date: Optional[str] = None) -> pd.DataFrame:
        """Fetches benchmark deposit rates using Baostock."""
        return _fetch_macro_data(bs.query_deposit_rate_data, "Deposit Rate", start_date, end_date)
Behavior1/5

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

With no annotations provided, the description carries full burden but offers no behavioral information. It doesn't indicate if this is a read/write operation, what data sources are used, potential rate limits, authentication needs, or what the output looks like. This is inadequate for a tool with parameters.

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 information. However, this conciseness comes at the cost of being under-specified rather than efficiently informative.

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 (4 parameters, no annotations, no output schema), the description is severely incomplete. It doesn't explain the tool's purpose, usage, behavior, or parameters, making it inadequate for an AI agent to understand and invoke the tool correctly.

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%, and the description mentions none of the 4 parameters (start_date, end_date, limit, format). It fails to explain what these parameters mean, their expected formats, or how they affect the benchmark deposit rates, leaving them completely undocumented.

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 'Benchmark deposit rates.' is a tautology that essentially restates the tool name 'get_deposit_rate_data' without adding meaningful specificity. It doesn't clarify what action is performed (e.g., retrieve, calculate, compare) or what resource is accessed, making it vague about the actual operation.

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 its many siblings (e.g., get_loan_rate_data, get_money_supply_data_month). There's no mention of context, prerequisites, or alternatives, leaving the agent with no usage direction.

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