Skip to main content
Glama
24mlight

A Share MCP

by 24mlight

get_money_supply_data_year

Retrieve yearly money supply data for economic analysis, supporting date ranges and multiple output formats to track monetary policy trends.

Instructions

Yearly money supply data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNo
end_dateNo
limitNo
formatNomarkdown

Implementation Reference

  • MCP tool handler: decorated with @app.tool(), invokes the use case via run_tool_with_handling for error handling and execution.
    @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)
    Invocation of the register_macroeconomic_tools function, which registers the get_money_supply_data_year tool among others.
    register_macroeconomic_tools(app, active_data_source)
  • Use case function that fetches yearly money supply data from the data source, applies validation and formatting.
    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)
  • Data source implementation: calls Baostock API via _fetch_macro_data to retrieve the raw yearly money supply data.
    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)
  • Abstract method definition in FinancialDataSource interface, defining the expected input/output for the data method.
    @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)."""
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. It reveals nothing about behavior: no indication of read/write nature, authentication needs, rate limits, error conditions, or what the output looks like. 'Yearly money supply data' suggests a read operation but lacks confirmation or details.

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?

Extremely concise with a single phrase 'Yearly money supply data.' It's front-loaded and wastes no words, though this brevity contributes to underspecification in other dimensions.

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?

For a 4-parameter tool with no annotations and no output schema, the description is incomplete. It doesn't cover parameter meanings, behavioral traits, or output format, leaving significant gaps 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.

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. It mentions 'yearly' which hints at date parameters but doesn't explain the four parameters (start_date, end_date, limit, format) or their relationships. The description adds minimal value beyond the schema titles.

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 the resource (money supply data) and temporal granularity (yearly), but lacks a specific verb and doesn't distinguish from sibling 'get_money_supply_data_month'. It's vague about what action is performed (retrieve? list? fetch?).

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?

No guidance on when to use this tool versus alternatives like 'get_money_supply_data_month' or other financial data tools. The description implies yearly data but doesn't specify use cases, prerequisites, or exclusions.

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