Skip to main content
Glama
zlinzzzz

FinData MCP Server

by zlinzzzz

stock_basic

Query basic stock data such as name, symbol, industry, and listing status by specifying stock code, name, market, exchange, or Hong Kong Stock Connect eligibility.

Instructions

Name:
    股票基础信息。

Description:
    获取股票的名称、代码等基础信息。

Args:
    | 名称       | 类型  | 必填 | 描述                                   |
    |------------|-------|------|----------------------------------------|
    | ts_code    | str   | 否    | 股票代码,每次只能查询一支股票    |
    | name       | str   | 否    | 股票名称 |
    | market     | str   | 否    | 市场类别 (主板/创业板/科创板/CDR/北交所) |
    | list_status    | str   | 否    | 上市状态(L:上市,D:退市,P:暂停上市。默认是L) |
    | exchange   | str   | 否    | 交易所代码 (上交所:SSE, 深交所:SZSE  北交所:BSE) |
    | is_hs   | str   | 否    | 是否沪深港通标的(N:否,H:沪股通,S:深股通) |
    | fields     | list  | 否    | 从Fields中选取需要查询的字段  |

Fields:
    - ts_code: TS代码
    - symbol: 股票代码
    - name: 股票名称
    - area: 地域
    - industry: 所属行业
    - fullname: 股票全称
    - enname: 英文全称
    - cnspell: 拼音缩写
    - market: 市场类型(主板/创业板/科创板/CDR)
    - exchange: 交易所代码
    - curr_type: 交易货币
    - list_status: 上市状态 L上市 D退市 P暂停上市
    - list_date: 上市日期
    - delist_date: 退市日期
    - is_hs: 是否沪深港通标的,N否 H沪股通 S深股通
    - act_name: 实控人名称
    - act_ent_type: 实控人企业性质

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ts_codeNo
nameNo
marketNo
list_statusNo
exchangeNo
is_hsNo
fieldsNo
Behavior2/5

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

No annotations provided; description lacks behavioral details such as read-only nature, data freshness, rate limits, or side effects. The tool is implicitly a query, but not stated.

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

Conciseness3/5

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

Well-structured with separate Args and Fields tables, but somewhat lengthy. Could be more concise without losing essential info.

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?

Comprehensive for a simple query tool: explains all parameters, includes return field descriptions. No output schema but fields table compensates. Complete context for basic stock info retrieval.

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 0% but the description includes a detailed table explaining each parameter's meaning, default, and possible values. The Fields table adds meaning to return values, compensates for lack of schema descriptions.

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?

Description clearly states it retrieves basic stock info (name, code, etc.), with a specific verb '获取' and resource '基础信息'. It distinguishes from financial statement tools like balancesheet but doesn't explicitly differentiate from sibling bak_basic.

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 on when to use this tool versus alternatives like bak_basic or other stock info tools. No explicit when-not-to-use or prerequisite conditions.

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