Skip to main content
Glama
openstockdata

stock-data-mcp

获取股票信息

stock_info

Retrieve basic stock information by providing a stock symbol and market code for Shanghai, Shenzhen, Hong Kong, and US markets.

Instructions

根据股票代码和市场获取股票基本信息, 不支持加密货币

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNo股票市场,仅支持: sh(上证), sz(深证), hk(港股), us(美股), 不支持加密货币sh
symbolYes股票代码(纯数字或字母组合,如600519、AAPL、HK00700)
Behavior3/5

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

No annotations are provided, so the description carries the burden. It implies a read operation and explicitly excludes crypto, but lacks details on error handling, rate limits, or what happens if the symbol is invalid. The information is adequate for a simple retrieval tool.

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 clear sentence with no unnecessary words. It is front-loaded with the action and resource, and directly states the constraint.

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?

The description does not specify the return format or field details. Since there is no output schema, the agent may need to infer what '基本信息' includes. In context of siblings that are more specific, this is somewhat incomplete but functional.

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 coverage is 100%, so the description adds little beyond what the schema already provides (market values and symbol format). The exclusion of crypto is already in the schema description for market, so no new meaning is added.

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 basic stock information by code and market, with an explicit exclusion of cryptocurrencies. This distinguishes it from other stock tools in the sibling list that focus on specific aspects like prices or financials.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear exclusion (no cryptocurrencies) giving guidance on when not to use. However, it does not explicitly compare with alternatives like stock_realtime or stock_prices, though the purpose is well-defined.

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/openstockdata/stock-data-mcp'

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