Skip to main content
Glama
lolifamily

ashare-mcp

get_financial_indicators

Fetch quarterly financial indicators for A-share stocks, including profitability, growth, turnover, balance sheet, cash flow, and DuPont decomposition ratios.

Instructions

Fetch a quarterly financial report; report selects which statement.

baostock splits quarterly fundamentals across six statements, each with a distinct field set. All values are cumulative-from-year-start: quarter=1 is 3-month, 2 is H1 (6-month), 3 is 9-month, 4 is FY (12-month).

report:

  • 'profit': profitability — roeAvg, npMargin, gpMargin, netProfit, epsTTM, MBRevenue, totalShare.

  • 'operation': turnover ratios — NRTurnRatio, INVTurnRatio, CATurnRatio, AssetTurnRatio (and matching *Days).

  • 'growth': YoY growth rates — YOYNI, YOYEPSBasic, YOYEquity, YOYAsset, YOYPNI.

  • 'balance': balance-sheet ratios — currentRatio, quickRatio, liabilityToAsset, assetToEquity. liabilityToAsset is rederived as 1 - 1/assetToEquity to work around stale upstream values (falls back to the raw value only when assetToEquity is null or zero).

  • 'cash_flow': cash-flow ratios — CFOToOR, CFOToNP, CFOToGr, CAToAsset.

  • 'dupont': DuPont ROE decomposition — dupontROE, dupontAssetTurn, dupontNitogr, dupontTaxBurden, dupontEbittogr.

Args: code: Stock code, e.g. 'sh.600519'. report: Which statement to fetch (see above). year: 4-digit year, e.g. '2024'. quarter: 1, 2, 3, or 4.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
reportYes
yearYes
quarterYes
Behavior4/5

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

Discloses that values are cumulative-from-year-start, the workaround for liabilityToAsset, and the distinct field sets for each report. Since no annotations are provided, the description carries the burden and does so well, though it omits output format or authorization needs.

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

Conciseness4/5

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

The description is well-structured with bullet sections for each report, but it is somewhat verbose. The initial sentence clearly states the purpose, and the detailed field lists are helpful, though slightly lengthy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 required parameters and no output schema, the description provides sufficient details to use the tool correctly, including data quirks and report options. It lacks only the return data structure, but that is partially mitigated by listing fields.

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

Parameters5/5

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

With 0% schema coverage, the description fully compensates by explaining the code example, listing all enum values for report with their fields, specifying year format, and indicating quarter values 1-4. Every parameter's meaning is clarified beyond the schema.

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

Purpose5/5

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

Specifically states 'Fetch a quarterly financial report' with the `report` parameter selecting the statement. The description lists each report type and its fields, clearly distinguishing this from sibling tools like get_financial_statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context about cumulative values and quarter meaning, and explains the data source's structure. However, it does not explicitly state when to use this tool versus alternatives like get_financial_statement, nor does it mention when not to use it.

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/lolifamily/ashare-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server