Skip to main content
Glama
xinkuang

China Stock MCP

by xinkuang

get_hist_data

Retrieves historical stock prices and technical indicators for Chinese stocks. Supports various date ranges, intervals, and adjustment methods.

Instructions

获取指定的股票历史行情数据及技术指标

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes股票代码 (例如: '000001')
intervalNo时间周期: minute, hour, day, week, month, year。默认:dayday
interval_multiplierNo时间周期乘数
start_dateNo开始日期,格式为 YYYY-MM-DD1970-01-01
end_dateNo结束日期,格式为 YYYY-MM-DD2030-12-31
adjustNo复权类型: none, qfq(前复权), hfq(后复权)。默认:nonenone
indicators_listNo要添加的技术指标,可以是逗号分隔的字符串(例如: 'SMA,EMA')或字符串列表(例如: ['SMA', 'EMA'])。支持的指标包括: SMA, EMA, RSI, MACD, BOLL, STOCH, ATR, CCI, ADX, WILLR, AD, ADOSC, OBV, MOM, SAR, TSF, APO, AROON, AROONOSC, BOP, CMO, DX, MFI, MINUS_DI, MINUS_DM, PLUS_DI, PLUS_DM, PPO, ROC, ROCP, ROCR, ROCR100, TRIX, ULTOSC。常用指标:SMA, EMA, RSI, MACD, BOLL, STOCH, OBV, MFI,建议不超过10个。SMA, EMA, RSI, MACD, BOLL, STOCH, OBV, MFI
output_formatNo输出数据格式: json, csv, xml, excel, markdown, html。默认: markdownmarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist, so the description carries full burden. It describes a read operation but lacks behavioral details such as rate limits, data freshness, or limitations. The simple statement of getting data is adequate but not transparent about any traits beyond that.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose.

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?

Given the complexity (8 parameters, enums, output formats) and the existence of an output schema (per context signals), the description is brief but sufficient. It does not explain default indicators or date ranges, but the schema covers detailed parameter documentation. The description could be more complete but is not incomplete.

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 baseline is 3. The description adds no additional meaning beyond the schema; it only restates the overall purpose. The schema already thoroughly describes each parameter.

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?

The description clearly states the tool retrieves specified historical stock data and technical indicators. It uses a specific verb ('get') and resource ('historical market data and technical indicators'), distinguishing it from siblings like get_realtime_data or get_stock_basic_info.

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?

No guidance is provided on when to use this tool versus alternatives, nor any conditions for use. The description only states what it does, not context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xinkuang/china-stock-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server