astrbot-mcp

kb_list

Lists documents in the knowledge base with pagination and tag filtering, so agents can browse or select stored entries.

Instructions

列出知识库中的文档。

Args: limit: 返回数量，1-500。 offset: 分页偏移。 tags: 逗号分隔的标签过滤。

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

Input Schema

Name	Required	Description	Default
`tags`	No
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden; '列出' implies a read-only operation but it never states this explicitly or notes safety/rate-limit behavior. It does add useful behavioral detail via the limit range (1-500) and pagination offset, though tag-filter semantics (AND/OR) are left unstated.

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 with the purpose, followed by a compact args block that maps to the parameters. There is no filler; the auto-generated 'Args:' formatting is terse but appropriate.

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?

For a simple 3-param list tool with an output schema, the purpose and all parameters are covered. But it omits routing guidance relative to kb_search and leaves tag-filter combination semantics undefined, which an agent browsing a large KB would need.

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 description coverage is 0%, yet the description documents all three parameters with value-adding detail: the 1-500 range for limit, pagination meaning for offset, and 'comma-separated' format for tags. This meaningfully compensates for the bare schema.

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 specific verb and resource ('列出知识库中的文档' – list documents in the knowledge base), which clearly signals a read/list operation. However, it does not distinguish itself from the overlapping sibling kb_search, leaving the agent to infer the difference.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus kb_search or kb_get, nor any statement about when not to use it. Usage is only implied by the verb 'list'.

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