PandaStock

Overview Schema Source Related Servers Discussions Admin

chDdxStockData

Fetch DDX large-order tracking data for a single stock by ticker code, helping analyze large-order activity and fund flow.

Instructions

获取个股DDX数据。Get DDX (large order tracking) data for one stock. Args: code (str): ticker like "600519".

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": {
      "code": "<code>"
    },
    "name": "chDdxStockData"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.5Sep 27, 2026

TDQS

C2.9/5.0

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 behavioral burden. 'Get' implies a read-only operation, but the description does not state authentication needs, rate limits, data freshness, or any behavior beyond the basic retrieval action.

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 compact and front-loads the purpose. The bilingual Chinese/English wording repeats the same information, but the overall size is appropriate for a simple one-parameter retrieval tool.

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?

An output schema exists, so the description need not explain return values. For a one-parameter tool with no annotations, however, the description remains thin on usage context and behavioral expectations, leaving some gaps for an agent.

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 description coverage is 0% for the single required parameter, so the description must compensate. It provides a useful ticker example ('600519'), but it does not explain exchange prefixes, market suffixes, or other valid identifier formats.

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?

The description states a specific verb and resource: get DDX (large order tracking) data for one stock. It clarifies the DDX acronym and the single-stock scope, but it does not distinguish this tool from sibling real-time or historical stock-data tools such as ChOneStockReal or chStockFrontDayHistory.

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 guidance is given on when to use this tool versus alternatives. The description implies it is for a single stock's DDX data, but there are no exclusions, prerequisites, or sibling comparisons.

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