Skip to main content
Glama
openstockdata

stock-data-mcp

获取A股指数历史价格

index_prices

Retrieve historical prices and technical indicators for A-share indices by code. Supports daily, weekly, or monthly periods with configurable data limit.

Instructions

根据A股指数代码获取指数历史价格及技术指标,例如 000300(沪深300)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo返回数量(int)
periodNo周期,如: daily(日线), weekly(周线), monthly(月线)daily
symbolNoA股指数代码,如: 000300(沪深300), 000001(上证指数)000300
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions getting 'historical prices and technical indicators' but lacks details on read-only nature, data freshness, rate limits, or whether it requires any authentication. Minimal behavioral disclosure.

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 with essential information and an example. No wasted words; efficient and front-loaded.

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 is sufficient for a simple tool with three optional parameters and no output schema. However, it lacks details on the output format, which could hinder an agent's understanding of the return value.

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 all parameters documented. The description adds an example (000300) but does not enrich parameter meaning beyond what the schema already provides. Baseline 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?

The description clearly states the tool retrieves historical prices and technical indicators for A-share indices, with a concrete example ('000300 for CSI 300'). It is distinct from sibling tools like stock_prices which focus on individual stocks.

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 implies usage for A-share indices but does not explicitly state when to use this tool versus alternatives (e.g., stock_prices for stocks, stock_prices_us for US stocks). No when-not or alternative guidance is provided.

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