Skip to main content
Glama
zwldarren

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Hist Data

get_hist_data

Retrieve historical stock prices for A, B, and H shares with configurable date ranges, intervals, and technical indicators.

Instructions

Get historical stock market data. 'eastmoney_direct' support all A,B,H shares

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adjustNoAdjustment typenone
sourceNoData sourceeastmoney
symbolYesStock symbol/ticker (e.g. '000001')
end_dateNoEnd date in YYYY-MM-DD format2030-12-31
fallbackNoTry the domain's other data sources when this one fails or has no data
intervalNoTime intervalday
recent_nNoNumber of most recent records to return
start_dateNoStart date in YYYY-MM-DD format1970-01-01
indicators_listNoTechnical indicators to add
interval_multiplierNoInterval multiplier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
+}
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed11 schema fields changedv1.0.0
    • removedInput schema / properties / adjust / title
      Removed value: -"Adjust"
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • removedInput schema / properties / indicators_list / title
      Removed value: -"Indicators List"
    • removedInput schema / properties / interval / title
      Removed value: -"Interval"
    • removedInput schema / properties / interval_multiplier / title
      Removed value: -"Interval Multiplier"
    • removedInput schema / properties / recent_n / title
      Removed value: -"Recent N"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
    • 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.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose a key non-obvious behavior: fallback order is 'eastmoney', 'eastmoney_direct', then 'sina', starting with the requested source. It also notes the coverage difference for A/B/H shares. It does not discuss errors or rate limits, but the output schema covers return expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, front-loaded with purpose, and every sentence conveys useful information about fallback and source coverage. A minor grammar issue ('support' instead of 'supports') and the slightly fragmented second sentence prevent a perfect score.

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?

For a 10-parameter tool with a fully described input schema and an output schema, the description covers the non-obvious parts: fallback ordering and share-class source coverage. It does not explicitly explain interactions like recent_n versus date ranges, but those are left to the parameter descriptions and do not need restating here.

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 real value by explaining the source hierarchy and that 'eastmoney_direct' has broader share-class coverage. This helps the agent choose the `source` parameter and understand `fallback` behavior without repeating the schema's own field descriptions.

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?

Opens with a specific verb and object — 'Get historical stock market data' — which clearly distinguishes it from get_realtime_data, news, and financial-statement siblings. The additional note about 'eastmoney_direct' supporting A/B/H shares further clarifies the data scope.

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 word 'historical' gives clear context for when this tool applies, and the fallback sentence explains how source selection works in practice. It does not explicitly name alternatives like get_realtime_data or state when not to use this tool, so it stops short of full routing guidance.

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