AgentLadle MCP AKShare

get_capital_flow

Read-onlyIdempotent

Retrieve capital flow time series for a stock to analyze money inflow and outflow trends over selected periods.

Instructions

Get capital flow time series for a stock.

Directly invoke with stock symbol. get_capital_flow(symbol="000001.SZ")

Args: symbol: Stock symbol (e.g. "000001.SZ") period: 1d/3d/5d/10d (default 1d)

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": {
      "symbol": "<symbol>"
    },
    "name": "get_capital_flow"
  }
}

Input Schema

Name	Required	Description	Default
`period`	No		1d
`symbol`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`hint`	No
`error`	No
`cached`	No
`source`	No
`status`	Yes
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint as true, which cover safety and idempotency. The description adds no further behavioral context (e.g., what the time series contains, data source, or limits). Minimal value added beyond annotations.

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 with a clear purpose sentence, but it includes redundant elements like a strategy tag that adds no new information. The args block repeats schema info. Overall efficient but could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of many sibling tools (e.g., get_quote, get_candlesticks) and no output schema details shown, the description fails to define what 'capital flow' is or how it should be interpreted. For a simple two-parameter tool, it lacks necessary context for correct usage.

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 schema description coverage is 0%, so the description must compensate. It provides an example for 'symbol' and lists allowed values for 'period' ('1d/3d/5d/10d') beyond the schema's default. However, it does not explain the meaning of 'period' (e.g., aggregation granularity).

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 clearly states 'Get capital flow time series for a stock' with a specific verb and resource. It distinguishes from many sibling tools by name, but does not explain the unique nature of capital flow vs other time series tools (e.g., get_quote, get_candlesticks).

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 provides no guidance on when to use this tool versus alternatives. The strategy tag says 'Directly invoke with stock symbol' but that is trivial and not comparative. No exclusions or context for selection among siblings are given.

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

Deploy Server