Skip to main content
Glama
qlib-sync

qlib-sync

cn_status

Read-only

Checks local A-share dataset freshness by reporting its latest trading date, size, stock pools, and whether newer community data exists; set offline to skip network checks.

Instructions

Report the local A-share data's latest trading date, size, and stock pools, and whether the community release has newer data (set offline=True to skip the network check).

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

Input Schema

NameRequiredDescriptionDefault
offlineNo

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 the description goes beyond them by disclosing that the call performs a network check against the community release and how to disable it. It does not say what happens when the network check fails or whether a stale/absent local dataset is reported as an error, which keeps it short of a 5 for a read-only open-world tool.

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?

A single sentence that front-loads the verb and the reported fields, with the parameter hint trailing in parentheses. It is efficient, though the compound noun list ('latest trading date, size, and stock pools') is slightly dense and could be enumerated for faster scanning.

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?

An output schema exists, so return values need not be described, and the read-only annotation covers safety. The remaining requirement for a one-parameter status tool is the network/offline behavior, which is stated; only failure-mode handling is absent.

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%, so the description must carry the parameter meaning, and it does: 'offline=True' is explained as skipping the network check. That is the only parameter and its effect is clear, though the default/behavior when omitted is left to the schema's default=false rather than restated.

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?

Uses a specific verb ("Report") with concrete resources: latest trading date, size, stock pools, and whether the community release has newer data. It is distinguishable from siblings like cn_health_check and cn_update, though it never names them explicitly to sharpen the boundary.

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 parenthetical gives actionable guidance for one parameter (set offline=True to skip the network check), which implies the when-to-use case of avoiding network access. However, it offers no explicit routing guidance against siblings such as cn_health_check or cn_list_pool, leaving the agent to infer which status tool to pick.

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