AgentLadle MCP AKShare

get_market_summary

Read-onlyIdempotent

Get market breadth snapshot with up/down/flat counts, limit counts, and total turnover for CN, HK, or US markets.

Instructions

Get market summary (up/down/flat counts, limit counts, total turnover).

Use for overall market breadth snapshot. get_market_summary(market="CN")

Args: market: CN/HK/US (default CN)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_market_summary"
  }
}

Input Schema

Name	Required	Description	Default
`market`	No		CN

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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds return content counts but does not disclose additional behavioral traits 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (2-3 sentences) with strategy and example. Front-loaded purpose. Every sentence adds value.

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?

Simple tool with one optional parameter, output schema exists, annotations cover safety. Description sufficiently explains purpose, parameters, and 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?

Schema has only one parameter with type and default. Description adds valid values (CN/HK/US) and default, improving agent understanding beyond schema.

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?

Clear verb 'Get' and resource 'market summary' with specific data points (up/down/flat counts, limit counts, total turnover). Distinct from siblings like get_market_status and get_market_anomaly.

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 tag explicitly states 'Use for overall market breadth snapshot.' Example provided. No exclusions or when-not-to-use, but context is clear.

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

Deploy Server