Skip to main content
Glama
qlib-sync

qlib-sync

cn_list_pool

Read-only

Lists members of a China A-share stock pool, such as CSI 300 or local pools, for a chosen date or the latest date.

Instructions

Members of a stock pool on a date (default: the latest date). Pools: all, csi100, csi300, csi500, csi800, csi1000, csiall, plus any local pools; cn_status lists what exists.

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

Input Schema

NameRequiredDescriptionDefault
dateNo
poolNocsi300

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the date defaults to the latest date, the pool values are enumerated, local pools are supported, and cn_status is identified as the discovery path. It does not describe return format, but an output schema exists.

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?

The description is two compact sentences with no wasted words. The core purpose and date default are front-loaded, and the pool enumeration and cn_status pointer follow efficiently.

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?

For a simple two-parameter read-only tool with an output schema and useful annotations, the description covers the essential context: what it returns, the date default, pool options, and where to discover local pools. Minor omissions such as date format and the default pool value are the only remaining gaps.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the burden of explaining parameters. It does well by listing the accepted pool values (all, csi100, csi300, csi500, csi800, csi1000, csiall, plus local pools) and by clarifying that the date defaults to the latest date. However, it does not specify the expected date format or restate that the pool default is csi300, leaving some semantic gaps.

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?

The description states the specific resource (members of a stock pool) and the scoping date, and it enumerates the pool values. It also distinguishes itself from cn_status, which is named as the tool for discovering what pools exist. The only weakness is that it opens with a noun phrase rather than a verb, but the purpose is still immediately clear.

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 provides an implied usage path by listing valid pools and pointing to cn_status for discovering what exists. It also clarifies the default date behavior. However, it does not explicitly say when to use this tool versus cn_get_prices or cn_update, nor does it state any exclusions, so guidance is adequate but incomplete.

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