Skip to main content
Glama

zwldarren-akshare-one-mcp

by ai.smithery
OverviewDiscussionsAdmin

get_hist_data

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

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
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / interval_multiplier / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / recent_n / anyOf
      Previous value: -[
-  {
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only offers minimal information about data source capabilities. It does not explain error handling for invalid symbols, rate limits, data availability periods, or whether the technical indicators are computed server-side or require specific parameters.

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 appropriately brief with two concise statements and no extraneous information. The purpose is front-loaded in the first sentence. The second sentence suffers from minor grammatical awkwardness ('support' instead of 'supports') but remains intelligible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 9 parameters—including technical indicators, multiple data sources, and date ranges—the description is insufficient. With no output schema or annotations to rely on, it should explain the return format, available data fields, and key parameter interactions, which it does not provide.

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?

Given 100% schema coverage, the baseline is adequate, but the description adds meaningful value by clarifying that eastmoney_direct supports all A/B/H shares, which helps users select the appropriate source parameter. However, it misses opportunities to explain technical concepts like qfq/hfq adjustments or the practical use of interval_multiplier.

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?

The description clearly states the core action ('Get') and resource ('historical stock market data'), distinguishing it from siblings like get_realtime_data and financial statement tools. The mention of A/B/H share support adds valuable scope context. However, it lacks specificity about what data points are actually returned (OHLCV prices, volume, etc.).

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 explicit guidance on when to use this tool versus alternatives like get_realtime_data or the financial metrics tools. While it hints that eastmoney_direct supports all A/B/H shares, it fails to explain source selection criteria or how to choose between date ranges versus the recent_n parameter.

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

All zwldarren-akshare-one-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources