Real-time Stock MCP Service

get_technical_indicators

Retrieve technical indicators such as MACD, KDJ, RSI, and BOLL for a specified stock via stock code. Optionally set the number of returned data points.

Instructions

获取指定股票的技术指标数据，包括MACD、KDJ、RSI、BOLL等技术指标和技术分析。

Args: stock_code: 股票代码，要在数字后加上交易所代码，格式如300750.SZ page_size: 返回数据条数，默认为30条

Returns: 技术指标数据的Markdown表格

Examples: - get_technical_indicators("300750.SZ") - get_technical_indicators("300750.SZ", 20)

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_technical_indicators"
  }
}

Input Schema

Name	Required	Description	Default
`stock_code`	Yes
`page_size`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 17, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states the return format (Markdown table) and default page_size, but omits data freshness, rate limits, or any side effects. Given the lack of annotations, this is insufficient for full transparency.

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?

The description is concise and well-structured with Args, Returns, and Examples sections. It is not overly verbose, but some sentences could be streamlined. The example is helpful.

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?

With an output schema present (not shown), the description does not need to detail return values. However, it lacks information on error handling, data range, or limitations. Given the tool's two parameters and output schema, it is moderately complete but could benefit from more context.

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?

Schema description coverage is 0%, so the description must compensate. It explains the stock_code format (e.g., '300750.SZ') and the default value for page_size (30). However, it does not clarify the meaning of page_size beyond '返回数据条数', which is partially addressed. Overall, it adds significant value over the bare schema.

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 that the tool retrieves technical indicator data (MACD, KDJ, RSI, BOLL) for a stock, with a specific verb '获取' and resource '技术指标数据'. It distinguishes itself from sibling tools by its unique function; no other sibling focuses on technical indicators.

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 provides usage via Args and Examples, but lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites or when not to use it, relying on implied usage from the example.

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