AgentLadle MCP AKShare

get_insider_trading

Read-onlyIdempotent

Retrieve insider trading records to track management buying and selling activities for a given stock symbol.

Instructions

Get insider trading records (高管增减持).

Use to track management buying/selling. get_insider_trading(symbol="000001.SZ")

Args: symbol: Security symbol

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

Input Schema

Name	Required	Description	Default
`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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety and idempotency. The description adds no additional behavioral context (e.g., data lag, pagination), so it provides minimal extra value beyond the 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 short and front-loads the main purpose. The <strategy> and <examples> tags add minor clutter but do not severely impact conciseness. Every sentence is functional, though the XML-like tags could be considered unnecessary.

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?

Given only one parameter and an existing output schema, the description is minimally adequate. However, it does not explain what insider trading records contain, how results are sorted, or any filtering options, leaving some gaps for an agent to infer.

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

Parameters2/5

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

With 0% schema description coverage, the description should add meaning to the 'symbol' parameter. It only restates 'symbol: Security symbol', which is already evident from the schema title. No format, examples, or constraints are provided, failing to compensate for the schema gap.

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?

The description clearly states 'Get insider trading records' with a specific verb and resource. The Chinese translation and strategy note add clarity. Among many sibling 'get_*' tools, this one uniquely targets insider trading, distinguishing it effectively.

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

Usage Guidelines3/5

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

The description includes a <strategy> tag ('Use to track management buying/selling'), providing some context on when to use the tool. However, it lacks explicit guidance on when not to use it or alternatives among sibling tools like get_institutional_holding or get_shareholder_top.

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

Deploy Server