Skip to main content
Glama
zwldarren

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Financial Metrics

get_financial_metrics

Retrieve key financial metrics from the three major financial statements for any stock symbol. Select data source with automatic fallback for reliability.

Instructions

Get key financial metrics from the three major financial statements.

With fallback on, the sources are tried as 'sina' and 'eastmoney_direct', starting with the requested one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoData sourceeastmoney_direct
symbolYesStock symbol/ticker (e.g. '000001')
fallbackNoTry the domain's other data sources when this one fails or has no data
recent_nNoNumber of most recent records to return

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / properties / fallback
      Added value: +{
+  "default": true,
+  "description": "Try the domain's other data sources when this one fails or has no data",
+  "type": "boolean"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "default": "eastmoney_direct",
+  "description": "Data source",
+  "enum": [
+    "sina",
+    "eastmoney_direct"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed4 schema fields changedv1.0.0
    • removedInput schema / properties / recent_n / title
      Removed value: -"Recent N"
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It adds value by explaining the fallback logic: when fallback is on, sources are tried in a specific order ('sina' then 'eastmoney_direct'), which is not stated in the schema. However, it does not disclose error handling, return format expectations, or whether the operation is read-only, though a 'get' implies safety. The fallback detail is useful but limited.

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 two sentences with no filler. The first sentence states the core purpose, and the second provides a key behavioral detail. It is front-loaded with the primary function and avoids redundancy with the schema. Every word earns its place.

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 that an output schema exists, the description does not need to explain return values. It covers the tool's purpose, the consolidation of three statements, and the critical fallback behavior. It could mention what specific metrics are included, but that is likely covered by the output schema. Overall, it provides sufficient context for an agent to call the tool correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so parameters are already documented. The description adds meaning to the interaction between 'source' and 'fallback' by clarifying the ordering of source attempts, which is not evident from the schema alone. This deepens the understanding of behavior, exceeding the baseline of 3 for full schema coverage.

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 states the tool retrieves 'key financial metrics from the three major financial statements,' a specific verb and resource. It distinguishes itself from siblings like get_balance_sheet, get_income_statement, and get_cash_flow by explicitly referencing all three statements at once. There is no ambiguity or tautology.

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?

The description implies this tool is for consolidated financial metrics across statements, which differentiates it from the individual statement tools, but it does not explicitly state when to choose this over siblings. There is no mention of alternatives or conditions for use, leaving the selection to inference. The fallback explanation provides some context for sourcing but not for tool choice.

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

Deploy Server

Other Tools