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

io.github.akfamily/aktools

Official
by akfamily

search_interfaces

Read-onlyIdempotent

Search AKShare data interfaces by keyword and get relevance-ranked results with interface names, Chinese titles, categories, and data sources, up to 50.

Instructions

按关键词搜索 AKShare 数据接口,结果按相关度排序,返回接口名、中文标题、类目与数据来源(source)。最多返回前 50 个。关键词描述数据类型,不要写证券名称或代码。同类数据常有多个来源:source 为“东方财富·行情(频繁访问易限流)”的接口,需要连续或批量取数时优先选其他来源的同类接口

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

Input Schema

NameRequiredDescriptionDefault
keywordYes关键词,多个关键词用空格分隔,如“A股 日线”“交易日历”“期货持仓”

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • changedInput schema / properties / keyword / description
      Previous value: -"关键词,匹配接口名或中文标题,如“历史行情”“交易日历”"New value: +"关键词,多个关键词用空格分隔,如“A股 日线”“交易日历”“期货持仓”"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: relevance ordering, a hard 50-result ceiling, and a rate-limiting warning attached to a specific data source, which affects how an agent plans repeated calls.

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?

The text is compact and front-loaded: purpose and return shape first, then the result cap, then keyword guidance, then the source-preference rule. The enumeration of returned fields is mildly redundant given the output schema, but every sentence otherwise carries actionable information.

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 read-only, single-parameter search tool with an output schema, the description covers what an agent needs to call it correctly: input semantics, result limit, ordering, and the source-selection caveat. Only the handoff to describe_interface/get_data is left implicit.

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?

With a single parameter and 100% schema description coverage, the schema already documents the keyword and its space-separated multi-keyword syntax with examples. The description adds only a modest constraint ('describe the data type, not security names or codes') beyond the schema's own examples, so it slightly exceeds the baseline rather than substantially expanding it.

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 a specific verb and resource ('按关键词搜索 AKShare 数据接口'), plus the sort order, returned fields, and a 50-result cap, so an agent knows exactly what this tool produces. It does not explicitly name the siblings describe_interface or get_data, so the differentiation is implied by the discovery role rather than stated.

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

Usage Guidelines4/5

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

It gives concrete usage constraints: the keyword should describe the data type, not security names or codes, and when fetching continuous or batch data the agent should prefer non-'东方财富·行情' sources. What's missing is explicit routing against the sibling tools (e.g., search first, then describe_interface, then get_data).

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