AgentLadle MCP AKShare

get_financial_metrics

Read-onlyIdempotent

Retrieve financial metrics time series including ROE, ROA, profit margins, and debt ratio for fundamental analysis across multiple reporting periods.

Instructions

Get financial metrics time series (ROE, ROA, margins, debt ratio).

Use for fundamental analysis over multiple periods. get_financial_metrics(symbol="000001.SZ", count=8)

Args: symbol: Security symbol count: Recent N periods (default 10)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_financial_metrics"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No
`symbol`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`hint`	No
`error`	No
`cached`	No
`source`	No
`status`	Yes
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true. The description adds that this is a time series tool, which is valuable context beyond annotations. No contradictions are present.

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 very concise: one sentence followed by a strategy tag and example call. Every element is useful and there is no redundant information.

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 the existence of an output schema, the description does not need to explain return values. It covers key aspects: time series nature, included metrics, and example usage. The annotations further ensure completeness for behavior.

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

Parameters3/5

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

The description repeats parameter names from the schema but adds minimal clarification: 'symbol: Security symbol' and 'count: Recent N periods (default 10)'. This is slightly better than the schema titles alone, but schema description coverage is 0%, and the added value is limited.

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?

The description clearly uses the verb 'Get' with the resource 'financial metrics time series' and lists specific metrics (ROE, ROA, margins, debt ratio). This effectively distinguishes it from sibling tools like 'get_financial_statement' or 'get_valuation'.

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

Usage Guidelines4/5

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

The <strategy> tag explicitly states 'Use for fundamental analysis over multiple periods,' providing clear context for when to use the tool. However, it does not mention when not to use or compare to alternatives like 'get_financial_report_latest'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server