stock_sz_a_spot_em
Retrieve real-time spot quotes for Shenzhen A-share stocks. Get up-to-date market data including price and volume for analysis.
Instructions
获取深A股实时行情数据
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回数据条数限制,默认为100条 |
Retrieve real-time spot quotes for Shenzhen A-share stocks. Get up-to-date market data including price and volume for analysis.
获取深A股实时行情数据
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回数据条数限制,默认为100条 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits like rate limits, data freshness, error handling, or consequences. Without annotations, the description carries the full burden, which it fails to meet.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, direct Chinese sentence that conveys the core purpose without fluff. While it could include more detail, it is appropriately sized for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one parameter and no output schema, the description provides minimal context. It does not mention what data is returned (fields, format) or any limitations. It is adequate but incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter (limit), with its description in the schema. The description adds no extra meaning beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves real-time market data for Shenzhen A-shares (深A股), with a specific verb (获取) and resource (深A股实时行情). Among sibling tools like stock_sh_a_spot_em for Shanghai A-shares, this uniquely identifies its target market.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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, such as when to prefer stock_sh_a_spot_em or stock_hk_spot_em. The description does not include any context about exclusive use cases or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/qiupo/marketMcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server