Skip to main content
Glama
Sign In
Real-time Stock MCP Service

Real-time Stock MCP Service

by DannyWongIsAvailable
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_holder_number

Retrieves historical shareholder count data and corresponding closing prices for a specified stock code.

Instructions

获取指定股票的股东户数数据，包括历史各期的股东人数及对应的收盘价。

Args: stock_code: 股票代码，要在数字后加上交易所代码，格式如688041.SH

Returns: 股东户数数据的Markdown表格

Examples: - get_holder_number("688041.SH")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stock_code": "<stock_code>"
    },
    "name": "get_holder_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
stock_codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/5.0
Behavior3/5

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

描述声明返回Markdown表格，隐含为只读操作，但未明确说明无副作用。由于注释未提供，描述承担披露责任，但未提及数据延迟、分页、错误处理等行为。不过对于简单查询工具，基本足够。

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?

描述包含目的、参数说明、返回值格式和示例，结构完整，信息密度适当，没有冗余。但篇幅略长，可进一步精简。

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?

工具只有一个参数且功能明确，描述涵盖了核心用途和参数格式，输出模式存在但未提供内容，描述说明了返回Markdown表格，基本满足使用需求。

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?

输入模式只有一个stock_code参数且描述覆盖率为0%，描述补充了股票代码格式示例（如688041.SH），增加了语义价值，帮助理解参数格式要求。

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?

描述明确说明了工具获取指定股票的股东户数数据，包括历史各期的股东人数及收盘价，动词'获取'清晰定义了操作，资源'股东户数数据'具体，与兄弟工具中其他金融指标区分明显。

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?

描述没有提供何时使用此工具 vs 其他兄弟工具的指导，也没有说明排除条件或先决条件，例如是否需要特定权限或数据范围。仅给出了基本功能描述，缺乏使用上下文。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools