AgentLadle MCP AKShare

get_security_list

Read-onlyIdempotent

Retrieve a list of securities for CN, HK, or US markets to discover valid symbol codes. Supports A-share board filtering and pagination.

Instructions

List securities for a market.

Use to discover valid symbol codes for a market. <critical_rules>market must be CN/HK/US. board: main/chinext/star/bse (CN only).</critical_rules> get_security_list(market="CN", count=50)

Args: market: Market code: CN / HK / US board: A-share board filter: main/chinext/star/bse (CN only, default all) count: Max results (default 100, max 1000) offset: Pagination offset (default 0)

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": {
      "market": "<market>"
    },
    "name": "get_security_list"
  }
}

Input Schema

Name	Required	Description	Default
`board`	No
`count`	No
`market`	Yes
`offset`	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.4/5.0

Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent. Description adds pagination limits and board constraints, enhancing behavioral understanding.

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?

Structured with strategy, rules, examples, and args. Slightly verbose but front-loaded with key purpose. Consistent with param docs.

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?

Covers input well; output shape not described but output schema exists. Annotations and rules provide sufficient context for correct usage.

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?

With 0% schema coverage, description fully documents all 4 parameters: markets, board options, count default/max, offset default. Compensates effectively.

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?

Clearly states it lists securities for a market and helps discover valid symbol codes. Distinct from siblings like get_quote or 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 Guidelines4/5

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

Strategy section explicitly says to use for discovering symbol codes. Critical rules provide valid market and board values. Lacks explicit when-not-to-use scenarios.

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

Deploy Server