AgentLadle MCP AKShare

get_candlesticks

Read-onlyIdempotent

Fetch OHLCV candlestick data for any asset class. Choose period, date range, and adjustment type.

Instructions

Get candlestick (OHLCV) data for any asset class.

Directly invoke with symbol. If asset_class is omitted, inferred from suffix. <critical_rules>

Symbol must be . (e.g. 000001.SZ, AAPL.US).
If both start/end and count given, start/end takes precedence. </critical_rules>

Args: symbol: Security symbol (e.g. "000001.SZ", "00700.HK", "AAPL.US", "000300.INDEX") asset_class: stock/index/fund/futures; inferred from suffix if omitted period: 1m, 5m, 15m, 30m, 60m, day, week, month (default day) start: Start date YYYY-MM-DD end: End date YYYY-MM-DD adjust: none/qfq/hfq (default none) count: Recent N bars (default 100, max 1000)

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_candlesticks"
  }
}

Input Schema

Name	Required	Default
`end`	No
`count`	No
`start`	No
`adjust`	No	none
`offset`	No
`period`	No	day
`symbol`	Yes
`asset_class`	No

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

A4.7/5.0

Behavior5/5

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

Annotations already indicate read-only, open-world, and idempotent behavior. Description adds operational constraints (symbol format, parameter precedence, default/max count) that go beyond annotations, providing comprehensive behavioral context.

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?

Well-structured with sections (strategy, critical rules, examples, Args). Front-loaded with purpose and usage. Slightly verbose but all content is valuable given the tool's complexity.

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

Completeness5/5

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

With output schema present, description focuses appropriately on input parameters and usage rules. Covers all necessary details for correct invocation, including defaults, constraints, and examples. No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, so description carries full burden. It explains all parameters with default values, allowed values (period), and meaning (symbol format). Adds significant value beyond the schema's titles and types.

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?

Description explicitly states 'Get candlestick (OHLCV) data for any asset class', using a specific verb and resource. It clearly distinguishes from sibling tools which cover different financial data types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit strategy for use (directly invoke with symbol, infer asset_class) and critical rules (symbol format, parameter precedence). Includes examples. Does not explicitly exclude alternative tools but gives enough context for correct invocation.

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

Deploy Server