AgentLadle MCP AKShare

get_ipo_calendar

Read-onlyIdempotent

Retrieve upcoming and recent IPO calendars for Chinese and Hong Kong markets to identify newly listed and forthcoming stocks.

Instructions

Get IPO calendar (upcoming and recent IPOs).

Use to find newly listed or upcoming stocks. get_ipo_calendar(market="CN")

Args: market: CN/HK (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_ipo_calendar"
  }
}

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

A3.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. Description merely restates the purpose without adding behavioral details 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.

Conciseness5/5

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

Description is extremely concise, front-loaded with the main purpose, and includes a strategy and example with no wasted words.

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?

Despite missing explicit sibling differentiation, the description combined with annotations and output schema provides sufficient completeness for a simple list tool.

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 coverage is 0%, but description explicitly defines the market parameter with values CN/HK and default CN, adding meaning beyond the schema.

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?

Description clearly states 'Get IPO calendar (upcoming and recent IPOs)' with a strategy tag emphasizing listing newly listed or upcoming stocks. It distinguishes from sibling get_ipo_detail implicitly by focusing on a calendar, not individual details.

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?

Strategy tag provides usage guidance ('Use to find newly listed or upcoming stocks'), but lacks explicit when-not-to-use or alternative tools like get_ipo_detail.

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

Deploy Server