Skip to main content
Glama
zwldarren

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Cash Flow

get_cash_flow

Retrieve company cash flow statements from Sina or Eastmoney with automatic fallback. Get recent records by stock symbol.

Instructions

Get company cash flow statement data.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoData sourcesina
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. Changed3 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"
+}
    • removedInput schema / properties / source / const
      Removed value: -"sina"
    • addedInput schema / properties / source / enum
      Added value: +[
+  "sina",
+  "eastmoney_direct"
+]
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed5 schema fields changedv1.0.0
    • removedInput schema / properties / recent_n / title
      Removed value: -"Recent N"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • 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

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It does add useful fallback ordering behavior ('sina' then 'eastmoney_direct'), but it omits other behavioral details such as error handling, data availability, or whether returned data is normalized. The read-only nature is implicit from 'get' rather than explicit.

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 concise: one purpose sentence and one behavioral sentence. It front-loads the main purpose and devotes a short paragraph to the fallback behavior. Every sentence earns its place without padding.

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 simple read-only nature, full schema documentation, and presence of an output schema, the description is largely sufficient. It explains the most non-obvious behavior (fallback ordering) but lacks any hint about when to prefer this tool over its financial-statement siblings.

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 coverage is 100%, so the baseline is 3. The description adds meaningful detail beyond the schema by explicitly naming the fallback source order and clarifying that the requested source is tried first. This helps agents understand how the 'source' and 'fallback' parameters interact.

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?

States a specific verb and resource: 'Get company cash flow statement data'. This clearly distinguishes it from sibling tools like get_balance_sheet and get_income_statement, making its purpose immediately recognizable.

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?

The description provides no guidance on when to use this tool versus sibling financial statement tools. It only explains fallback behavior, not selection criteria or exclusions. An agent must infer that cash flow data is requested when cash flow statements are needed.

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