akshare-one-mcp

Overview Schema Source Related Servers Discussions Admin

Get Hist Data

get_hist_data

Retrieve historical stock data for a symbol across custom dates and intervals, with optional price adjustments and technical indicators. Fallback sources maintain access when a selected source fails.

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', 'sina' and 'ths', starting with the requested one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_hist_data"
  }
}

Input Schema

Name	Required	Description	Default
`adjust`	No	Adjustment type	none
`source`	No	Data source	eastmoney
`symbol`	Yes	Stock symbol/ticker (e.g. '000001')
`end_date`	No	End date in YYYY-MM-DD format	2030-12-31
`fallback`	No	Try the domain's other data sources when this one fails or has no data
`interval`	No	Time interval	day
`recent_n`	No	Number of most recent records to return
`start_date`	No	Start date in YYYY-MM-DD format	1970-01-01
`indicators_list`	No	Technical indicators to add
`interval_multiplier`	No	Interval multiplier

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.0Oct 24, 2026

changedInput schema / properties / source / enum

Previous value: -[
-  "eastmoney",
-  "eastmoney_direct",
-  "sina"
-]New value: +[
+  "eastmoney",
+  "eastmoney_direct",
+  "sina",
+  "ths"
+]

Changed1 schema field changedv0.4.0Sep 22, 2026

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"
+}

Changed1 schema field changedv0.1.2May 1, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed11 schema fields changedv1.0.0Jan 3, 2026
- 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"
```
First observedAug 14, 2025

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavior: the fallback source ordering ('eastmoney', 'eastmoney_direct', 'sina', 'ths' starting with the requested one). It does not state read-only status, what happens when all sources fail, or return characteristics.

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?

Two short sentences, front-loaded with purpose, followed by the source-coverage caveat and the fallback ordering. The second sentence is slightly awkwardly phrased but every clause carries information.

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 read tool with a full output schema and 100% schema coverage, the description covers the main hidden behavior (source fallback ordering and coverage). Remaining gaps—read-only confirmation and failure behavior—are minor given the output schema and rich parameter documentation.

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 the baseline is 3; the description adds real value by explaining the semantic difference between source values ('eastmoney_direct' supports all A,B,H shares) and the precise order in which sources are tried for `fallback`, which the schema only describes generically.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get historical stock market data'), which clearly distinguishes it from the realtime sibling get_realtime_data. It does not name any sibling explicitly, so it stops short of full sibling differentiation.

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?

Usage is implied rather than stated: 'historical' hints at when to pick this over get_realtime_data, and the note that 'eastmoney_direct' supports all A,B,H shares is a partial hint about source selection. There is no explicit when/when-not guidance or named alternative.

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

Deploy Server