Retrieve whole-market capital flow data for Shanghai, Shenzhen, and Beijing A-shares to track institutional money movement and support market analysis.
获取市场资金流向。Get whole-market capital flow. No arguments.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.5.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. The verb 'Get' implies a read-only retrieval operation, and 'No arguments' confirms a parameterless call, but there is no mention of authentication, rate limits, data freshness, or other operational traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short and front-loaded: it states the resource first and the no-argument fact second. The bilingual repetition is compact and there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter market-data tool with an output schema, the description is nearly complete: it identifies the data returned and confirms no inputs. It lacks usage context and operational details, but the output schema removes the need to explain return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and the schema description coverage is already complete. The description's 'No arguments' merely confirms what the schema shows, so the baseline score of 4 for a zero-parameter tool is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb (获取/Get) and resource (whole-market capital flow), and the word 'whole-market' distinguishes it from sibling tools such as ChStockCurReal, ChConceptCurReal, and ChIndustryCurReal. An agent can identify the tool's general function without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says only 'No arguments,' which is invocation information rather than usage guidance. It does not state when to use this tool instead of related market-data siblings or what conditions make it appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.