Skip to main content
Glama
zwldarren

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Balance Sheet

get_balance_sheet

Retrieve a company's balance sheet by stock symbol, with optional data source selection and automatic fallback to alternate sources.

Instructions

Get company balance sheet 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. 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": "sina",
+  "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?

There are no annotations, so the description carries the behavioral disclosure burden. It does add a meaningful non-obvious behavior: when fallback is enabled, sources are tried as 'sina' and 'eastmoney_direct', starting with the requested one. However, it does not describe failure behavior when fallback is disabled, potential output variations between sources, or explicit read-only/safety characteristics beyond the word 'Get'.

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 concise sentences with no filler or repetition. The core purpose is front-loaded in the first sentence, and the fallback behavior is efficiently explained in the second. Every sentence 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 the presence of an output schema and fully described parameters, the description is mostly sufficient for an agent to call the tool correctly. It covers the main non-obvious behavior (fallback ordering), though it could add explicit sibling-selection guidance and failure behavior. These gaps are minor given the schema richness.

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 value by clarifying the interaction between `source` and `fallback`: it specifies the exact fallback order and that the requested source is tried first. This goes slightly beyond the schema's generic 'try the domain's other data sources' wording.

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 states a clear verb and resource: 'Get company balance sheet data.' This distinguishes it from sibling tools like get_income_statement and get_cash_flow, which target different financial statements. The purpose is immediately recognizable and unambiguous.

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 does not explicitly state when to use this tool versus alternatives such as get_income_statement or get_cash_flow. The intended usage is implied by the phrase 'balance sheet data,' but no direct when-to-use or when-not-to-use guidance is provided. The fallback sentence explains source selection behavior, not usage context.

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