Skip to main content
Glama
Sign In
zwldarren

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Realtime Data

get_realtime_data

Retrieve real-time stock quotes for A, B, and H shares from Chinese markets, with configurable data sources and fallback when a source fails or returns no data.

Instructions

Get real-time stock market data. 'eastmoney_direct' support all A,B,H shares

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

Input Schema

NameRequiredDescriptionDefault
sourceNoData sourceeastmoney_direct
symbolNoStock symbol/ticker (e.g. '000001')
fallbackNoTry the domain's other data sources when this one fails or has no data

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "eastmoney_direct",
-  "eastmoney",
-  "xueqiu"
-]New value: +[
+  "eastmoney_direct",
+  "eastmoney",
+  "xueqiu",
+  "ths"
+]
  2. 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"
+}
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "xueqiu",
-  "eastmoney",
-  "eastmoney_direct"
-]New value: +[
+  "eastmoney_direct",
+  "eastmoney",
+  "xueqiu"
+]
  3. Changed1 schema field changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed4 schema fields changedv1.0.0
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  5. First observed

TDQS

A3.5/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 behavioral burden. It usefully discloses the fallback source ordering and that 'eastmoney_direct' supports all A/B/H shares, but it does not mention read-only nature, rate limits, data latency, or behavior when no data exists.

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 and front-loads the core purpose. However, the second sentence is grammatically awkward ('support all' and an incomplete clause), slightly reducing clarity.

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

Completeness3/5

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

The output schema covers return values and the schema covers parameters, but the description does not explain what happens when symbol is null, nor which sources support which market types beyond a note about 'eastmoney_direct'. For a tool with three optional parameters and multiple sources, this leaves some ambiguity.

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 beyond the schema by explaining that 'eastmoney_direct' supports all A, B, and H shares and by specifying the exact fallback ordering among sources.

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 a specific verb and resource: getting real-time stock market data. The 'real-time' qualifier implicitly distinguishes it from sibling get_hist_data, but it does not explicitly name or contrast with that sibling.

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 by 'real-time stock market data', but there is no explicit guidance on when to choose this tool over get_hist_data or other siblings. The fallback behavior is described, but not the decision criteria for using this tool versus alternatives.

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