Skip to main content
Glama
qlib-sync

qlib-sync

cn_get_prices

Read-only

Retrieve daily A-share price bars for up to 20 symbols across a date range, with selectable fields and raw or adjusted prices for market analysis.

Instructions

Daily bars for up to 20 A-share symbols between start and end (YYYY-MM-DD, inclusive; end defaults to the latest date).

    fields: any of open, high, low, close, vwap, volume, amount, change, factor
    (default open, high, low, close, volume, change). change is the daily return as a
    fraction (0.01 = +1%). price_basis="raw" gives real traded prices and share volume;
    "adjusted" gives Qlib's split- and dividend-adjusted series. Rows are capped by max_rows.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>",
      "start": "<start>"
    },
    "name": "cn_get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startYes
fieldsNo
symbolsYes
max_rowsNo
price_basisNoraw

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 safety is covered; the description adds materially useful behavior: rows are capped by max_rows (truncation risk), the default field set when none is supplied, and the exact meaning of price_basis raw vs adjusted. The only omission is what happens on truncation (silent cut vs error) and rate limits.

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?

Front-loaded and dense in a good way: the core scope is in the first sentence and every subsequent clause adds a fact an agent would otherwise have to guess. The field enumeration and price_basis explanation could be slightly tighter, but nothing is redundant.

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-value explanation is not required, and the description covers defaults, caps, and value semantics for a moderately complex 6-parameter tool. It falls just short because the symbol identifier format and truncation behavior remain unspecified, both of which affect whether a call succeeds.

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?

With 0% schema description coverage the description carries the full burden, and it does most of it: start/end format and inclusivity, end defaulting to the latest date, the complete allowed field list plus defaults, the fraction meaning of change, max_rows as a cap, and the raw/adjusted semantics. The gap is the symbol string format (e.g. exchange prefix/suffix), which is left unspecified for the single most important required parameter.

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?

The description opens with a specific verb+resource: daily OHLCV bars for A-share symbols within a start/end date range. It also states a hard scope limit (up to 20 symbols) and the inclusive date semantics, which is enough to distinguish it from the listed siblings (health check, list pool, status, update), none of which are price-fetching tools.

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?

Usage context is implied rather than stated: the 20-symbol cap, the inclusive date range, and the default end date tell an agent what shape of request is valid. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. for adjusted vs raw histories or multi-universe queries), so an agent must infer routing.

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