PandaStock

Overview Schema Source Related Servers Discussions Admin

ChStockCurReal

Retrieve a real-time snapshot of all A-share stocks in one call, covering Shanghai, Shenzhen, and Beijing markets without any arguments.

Instructions

获取A股实时行情快照。Get realtime snapshot of ALL A-share stocks. No arguments.

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": "ChStockCurReal"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.5Sep 27, 2026

TDQS

B3.4/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 the full burden. It does disclose the two most relevant behavioral facts for this tool: the scope is ALL A-share stocks (implying a large payload) and it takes no arguments. It says nothing about update frequency beyond 'realtime', rate limits, or whether the snapshot is a single point in time, which is a real gap for a live-quote feed.

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?

Two short sentences, front-loaded, with the scope stated immediately. The bilingual restatement is redundant, but the whole definition is only a dozen words and nothing is buried.

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?

With an output schema present, return-value documentation is not needed, and a zero-parameter read tool has a shallow contract. What remains missing is freshness/update-cadence context and routing guidance against the many sibling realtime tools.

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 tool takes zero parameters, so the baseline is 4. The description's 'No arguments' correctly reinforces the empty schema and prevents the agent from hunting for ticker or date inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: fetch a realtime snapshot of ALL A-share stocks. The word 'ALL' plus the zero-parameter shape distinguishes it from ChOneStockReal and the market/concept/industry variants, although no sibling is named explicitly.

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?

The description offers no when-to-use guidance. It never contrasts itself with ChOneStockReal (single-stock realtime) or ChStockFrontDayHistory (historical), so the agent must infer selection from the name and the 'ALL' scope alone.

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