AgentLadle MCP AKShare

list_macro_indicators

Read-onlyIdempotent

List available macro indicators (GDP, CPI, PMI) filtered by country or keyword to obtain indicator codes for subsequent data retrieval.

Instructions

List available macro indicators (GDP, CPI, PMI, etc.).

Use first to discover indicator_code, then pass to get_macro_data. list_macro_indicators(country="CN")

Args: keyword: Filter keyword (optional) country: CN/US/HK/JP/EU (optional) count: Max results (default 100)

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": "list_macro_indicators"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No
`country`	No
`keyword`	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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint as true, so safety is clear. The description adds useful context (preparatory step for get_macro_data) but does not disclose any additional behavioral traits beyond what annotations cover.

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?

Description is concise and front-loaded with purpose. The embedded strategy and example tags are unconventional but add value without excessive length. No redundant information.

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?

Given the tool has 3 optional parameters, no required fields, and an output schema exists, the description fully covers what an agent needs: what the tool does, how to use it, and how it fits into a workflow (paired with get_macro_data).

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% (no param descriptions in schema), so description must compensate. It clarifies 'country' values (CN/US/HK/JP/EU), 'count' default and max behavior, and 'keyword' as optional filter. Adds meaning beyond schema types and defaults.

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 available macro indicators such as GDP, CPI, PMI, and explicitly connects to get_macro_data by suggesting discovery of indicator_code. Distinguishes from siblings like get_macro_data.

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

Usage Guidelines5/5

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

Explicitly provides strategy: 'Use first to discover indicator_code, then pass to get_macro_data.' Also includes an example invocation with 'country' parameter, guiding correct usage.

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

Deploy Server