Skip to main content
Glama
zwldarren

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Income Statement

get_income_statement

Retrieve a company's income statement by stock symbol, with optional data source fallback to ensure reliable results.

Instructions

Get company income 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. 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
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly explains the non-obvious fallback behavior: with fallback on, sources are tried as 'sina' and 'eastmoney_direct', starting with the requested one. This adds meaningful insight beyond the schema and helps the agent anticipate multi-source selection behavior.

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 compact and front-loaded with the core purpose in the first sentence. The second sentence adds genuinely useful behavioral detail without redundancy or fluff. 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 the output schema exists, return-value documentation is unnecessary. The description covers the main behavioral nuance (fallback source ordering) and the schema covers parameter semantics. Minor gaps remain around when to prefer each source and what happens when both sources fail, but these are not blocking for correct invocation.

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?

Schema description coverage is 100%, so the schema already documents all four parameters. The description adds some value by clarifying how the fallback parameter interacts with source ordering, but it does not elaborate on symbol or recent_n semantics beyond what the schema already provides.

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 uses a specific verb ('Get') and a specific resource ('company income statement data'), making the tool's purpose immediately clear. It also distinguishes itself naturally from sibling tools like get_balance_sheet and get_cash_flow, which target different financial statements.

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 usage: use this when you need income statement data. However, it does not explicitly explain when to choose this over the sibling financial tools, nor does it provide exclusions or alternative recommendations. The fallback explanation is about 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