Skip to main content
Glama
zwldarren

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Realtime Data

get_realtime_data

Fetch real-time stock quotes for A, B, and H shares, with automatic fallback to alternate sources for dependable 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' and 'xueqiu', starting with the requested one.

Input Schema

TableJSON 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

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"
+}
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "xueqiu",
-  "eastmoney",
-  "eastmoney_direct"
-]New value: +[
+  "eastmoney_direct",
+  "eastmoney",
+  "xueqiu"
+]
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. 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"
  4. 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 provided, the description carries the full burden of behavioral disclosure. It does add useful behavior: the fallback source chain and that 'eastmoney_direct' supports A/B/H shares. However, it does not describe data freshness, error behavior, or what happens when fallback is disabled.

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 compact and front-loaded with the core purpose. The second sentence efficiently explains the fallback mechanism. Minor grammar issues ('support all A,B,H shares') detract slightly, but no wasted words are present.

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 3-parameter read-oriented tool with full schema coverage and an output schema, the description is largely sufficient. It covers the main behavioral nuance (fallback order) and source scope. Missing only explicit 'when to use' guidance and source-specific limitations.

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 three parameters. The description adds a bit of context about source fallback and share-class support, but it does not materially expand on parameter semantics beyond what the schema provides.

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 tool's purpose: 'Get real-time stock market data.' It identifies the resource (stock market data) and the timing (realtime), which distinguishes it from sibling tools like get_hist_data or get_news_data, though it does not explicitly name those alternatives.

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 the tool is for real-time stock data and explains the fallback source order, which gives some usage context. However, it does not explicitly state when to use this tool over the siblings, nor does it provide exclusions or guidance on choosing between the three sources.

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