Skip to main content
Glama
zlinzzzz

FinData MCP Server

by zlinzzzz
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

stock_company

Retrieve basic information of listed companies such as company name, registration details, management, and business scope. Filter by stock code or exchange.

Instructions

Name:
    上市公司基本信息。

Description:
    获取上市公司基础信息。

Args:
    | 名称       | 类型  | 必填 | 描述                                   |
    |------------|-------|------|----------------------------------------|
    | ts_code    | str   | 否    | 股票代码，每次只能查询一家公司    |
    | exchange   | str   | 否    | 交易所代码 (上交所：SSE， 深交所：SZSE  北交所：BSE) |
    | fields     | list  | 否    | 从Fields中选取需要查询的字段  |

Fields:
    - ts_code：股票代码
    - com_name：公司全称
    - com_id：统一社会信用代码
    - exchange：交易所代码
    - chairman：法人代表
    - manager：总经理
    - secretary：董秘
    - reg_capital：注册资本(万元)
    - setup_date：注册日期
    - province：所在省份
    - city：所在城市
    - introduction：公司介绍
    - website：公司主页
    - email：电子邮件
    - office：办公室
    - employees：员工人数
    - main_business：主要业务及产品
    - business_scope：经营范围

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ts_codeNo
exchangeNo
fieldsNo

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the operation is read-only, any authentication requirements, rate limits, or side effects beyond stating it 'gets' data.

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 well-structured with sections (Name, Description, Args, Fields) and uses Markdown. It is somewhat lengthy but each part adds value. Could be slightly more concise.

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?

Given no output schema and no annotations, the description covers parameter details and return fields adequately. However, it lacks explanation of behavior when multiple parameters are combined, and does not specify the output format or edge cases.

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 description coverage is 0%, but the tool description provides detailed parameter descriptions in Chinese, including constraints (e.g., '每次只能查询一家公司') and enum values for exchange. This adds significant meaning beyond the schema.

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 retrieves basic company information ('获取上市公司基础信息'). The name 'stock_company' aligns with this purpose. However, it does not differentiate from sibling tool 'stock_basic', which may have overlapping functionality.

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?

The description mentions that only one company can be queried at a time and allows selecting fields, but provides no guidance on when to use this tool versus alternatives (e.g., stock_basic) or when not to use it.

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