Skip to main content
Glama
zlinzzzz

FinData MCP Server

by zlinzzzz

daily

Retrieve daily non-adjusted market data for A-share stocks, including open, high, low, close, volume, and amount, filtered by date or stock code.

Instructions

Name:
    A股日线行情。

Description:
    获取股票未复权的日线行情数据。

Args:
    | 名称       | 类型  | 必填 | 描述                                   |
    |------------|-------|------|----------------------------------------|
    | ts_code    | str   | 否    | 股票代码(支持多个股票同时提取,逗号分隔) |
    | trade_date | str   | 否    | 交易日期(YYYYMMDD),不与start_date和end_date同时出现 |
    | start_date | str   | 否    | 开始日期(YYYYMMDD),与end_date同时出现 |
    | end_date   | str   | 否    | 结束日期(YYYYMMDD),与start_date同时出现  |
    | fields     | list  | 否    | 从Fields中选取需要查询的字段  |

Fields:
    - ts_code: 股票代码
    - trade_date: 交易日期
    - open: 开盘价
    - high: 最高价
    - low: 最低价
    - close: 收盘价
    - pre_close: 昨收价【除权价,前复权】
    - change: 涨跌额
    - pct_chg: 涨跌幅 【基于除权后的昨收计算的涨跌幅:(今收-除权昨收)/除权昨收】
    - vol: 成交量 (手)
    - amount: 成交额 (千元)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ts_codeNo
trade_dateNo
start_dateNo
end_dateNo
fieldsNo
Behavior2/5

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

No annotations provided, and the description lacks behavioral traits such as rate limits, permissions, or data freshness. It only mentions the unadjusted nature and parameter constraints like mutual exclusivity of trade_date with start_date/end_date.

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?

Well-structured with tables and bullet points, but includes a redundant 'Name:' line. The description is clear and not overly verbose, though could be slightly more concise.

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 lack of output schema, the description provides the available fields and explains them. Parameters are fully documented. However, it omits details on pagination, error handling, default behavior when no parameters are given, and historical data range.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description thoroughly documents all 5 parameters: ts_code (supports multiple stocks), trade_date (format and mutual exclusivity), start_date/end_date (must be used together), and fields (select from listed fields). It also lists available output fields with meanings.

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 A-share daily market data without adjustment using specific verb '获取' and resource '日线行情数据'. It distinguishes from sibling tools like balance sheet or cash flow data.

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 explicit guidance on when to use this tool vs alternatives. The description implies usage for daily price data but does not provide exclusion criteria or comparison to other tools.

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/zlinzzzz/finData-mcp-server'

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