Skip to main content
Glama
io.github.akfamily/aktools

io.github.akfamily/aktools

Official
by akfamily

get_data

Read-onlyIdempotent

Fetches financial data from AKShare interfaces using a specified interface name and parameters, supporting row limits and offset pagination; returns row counts and a CSV download URL when run as an HTTP service.

Instructions

调用 AKShare 接口获取数据。一次最多返回 max_rows 行,用 offset 翻页或取最后若干行;返回总行数与本次的起始行,随 HTTP 服务运行时还给出完整数据的 CSV 下载地址

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": {
      "name": "<name>"
    },
    "name": "get_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes接口名,如 stock_zh_a_hist_em
offsetNo从第几行开始返回(从 0 开始);负数表示从末尾倒数,如 -20 取最后 20 行
paramsNo接口参数,如 {"symbol": "000001", "start_date": "20240101"}
max_rowsNo最多返回的行数,默认 100

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • changedInput schema / properties / name / description
      Previous value: -"接口名,如 stock_zh_a_hist"New value: +"接口名,如 stock_zh_a_hist_em"
  2. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "从第几行开始返回(从 0 开始);负数表示从末尾倒数,如 -20 取最后 20 行",
      +  "title": "Offset",
      +  "type": "integer"
      +}
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world behavior, so the bar is lower. The description still adds genuine context beyond them: a per-call row cap, the pagination contract, that the response reports total rows plus this batch's start row, and that an HTTP-mode deployment also returns a CSV download URL for the full dataset.

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?

Two dense sentences with no filler, and the row-cap limit is front-loaded ahead of the pagination advice. The clause about the CSV download URL is somewhat parenthetical but still earns its place by explaining a conditional response field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return-value explanation is partly redundant, and the description never explains how to obtain a valid `name` or discover an interface's `params` — the key gap for a generic dispatcher. It is otherwise complete enough to call the tool correctly for a known interface.

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 coverage is 100%, so the baseline is 3; every parameter including name, offset, params and max_rows is already documented in the schema. The description restates the offset/max_rows behavior but adds no new syntax, format, or constraint details beyond what the schema provides.

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?

States a concrete verb and resource: invoke an AKShare interface by name and return rows of data. That distinguishes it from the describe_interface/search_interfaces siblings by implication (this is the one that actually fetches), though it never says so explicitly.

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?

Gives real operational guidance for pagination: use offset to page forward or a negative offset to take the last N rows. However it gives no guidance on the sibling relationship — nothing tells the agent to call search_interfaces to find a name or describe_interface to learn an interface's params before fetching, which is the main misuse risk for a dispatcher tool.

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