Skip to main content
Glama
terrysun1216

ahshare-mcp

by terrysun1216

get_fund_holdings

Retrieve the complete fund holdings for a stock, including all funds, codes, shares held, percentage of float, and market value.

Instructions

获取股票基金持股明细(全量,不限前10)。返回所有持有该股票的基金名称、代码、持仓数量、占流通股比例、持股市值

Input Schema

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

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

No annotations provided, so description carries full burden. It discloses that the tool returns specific fields (fund names, codes, quantities, etc.) and implies it is a read operation. Lacks information on authentication or rate limits, but for a simple query tool, this is reasonable.

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?

Single sentence that is front-loaded with the core action and key distinguishing feature. Every word serves a purpose, no redundancy.

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?

Given simple structure (1 param, no output schema), description adequately explains what is returned and the scope. Could mention potential large result sets or lack of pagination, but overall sufficient.

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%, with description of symbol already in schema. Description does not add significant extra meaning beyond what schema provides, so baseline score of 3 is appropriate.

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?

Description clearly specifies verb '获取' and resource '股票基金持股明细', and explicitly distinguishes itself from siblings like get_top10_shareholders by noting '全量,不限前10' (full amount, not limited to top 10).

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?

Provides clear context that this tool returns all holdings, not just top 10, implying when to use it over sibling tools that return top 10 shareholders. However, it does not explicitly mention when not to use or list alternatives.

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