Real-time Stock MCP Service

get_current_plate_changes

Retrieve current intraday sector anomaly data including price changes, capital flows, and anomalous stocks, sorted by total anomaly count. Supports optional page size parameter.

Instructions

获取当日板块异动数据，包括各板块的涨跌幅、主力资金流向以及板块内异动个股等信息（异动总次数降序）。

Args: page_size: 返回数据条数，默认为10条

Returns: 格式化的当日板块异动数据，以Markdown表格形式展示

Examples: - get_current_plate_changes() - get_current_plate_changes(30)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_current_plate_changes"
  }
}

Input Schema

Name	Required	Description	Default
`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.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that data is for the current day, sorted descending, and returns a Markdown table. However, it does not mention side effects, authorization needs, rate limits, or error handling, leaving gaps in behavioral transparency.

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 concise with one clear sentence for purpose, followed by structured sections for Args, Returns, and Examples. No redundant information, and the length is appropriate for the tool's simplicity.

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 the tool has one optional parameter and an output schema exists, the description covers key aspects: purpose, parameter, return format (Markdown table), ordering, and examples. It lacks error handling details but is complete enough for a simple data retrieval tool.

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?

The description adds meaning to the 'page_size' parameter beyond the schema by explaining it controls the number of returned entries (默认10条). Schema has no description field for the parameter, so the description compensates effectively.

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 current-day plate changes data, including rise/fall percentages, main capital flow, and abnormal stocks, sorted by total abnormal count descending. It specifies the verb '获取' and resource '板块异动数据', distinguishing it from sibling tools like get_plate_fund_flow or get_plate_quotation.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention when to avoid it or provide comparisons with sibling tools like get_plate_fund_flow. The usage context is implied but not clearly stated.

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