Skip to main content
Glama
terrysun1216

ahshare-mcp

by terrysun1216

get_top10_free_shareholders

Get top 10 free shareholders of a stock with details on name, type, share count, and percentage of tradable shares.

Instructions

获取股票十大流通股东数据(仅流通股),包括股东名称、股东类型、持股数量、占流通股比例

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol/ticker (e.g. '600519')
Behavior2/5

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

No annotations are provided. The description lists the output fields but does not disclose behavioral traits such as data recency, ordering, pagination, or any side effects. For a data retrieval tool, this minimal disclosure leaves the agent without important context.

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, concise sentence that efficiently states the tool's purpose and output fields. No unnecessary words or repetition.

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?

For a simple tool with one parameter and no output schema, the description provides the essential fields but lacks behavioral context (e.g., data source, update frequency). It is minimally adequate but not comprehensive.

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?

The schema already documents the single 'symbol' parameter with a description. The tool description does not add new meaning beyond the schema, so the baseline score of 3 applies given 100% schema coverage.

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 data on the top 10 tradable shareholders (流通股), including specific fields. The name and description together distinguish it from the sibling tool 'get_top10_shareholders' by specifying 'free' (tradable).

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

Usage Guidelines3/5

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

The description explains what data is returned but does not provide guidance on when to use this tool versus the sibling 'get_top10_shareholders' or other related tools. Usage context is implied by the tool name, but no explicit when-to-use or when-not-to-use advice is given.

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/terrysun1216/ahshare-mcp-ts'

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