Skip to main content
Glama

列知识库空间

feishu_wiki_spaces
Read-only

Lists Feishu wiki spaces available to the bot, returning space IDs and names so you can select a space before listing its root wiki nodes.

Instructions

列出机器人能看到的飞书知识库(wiki)空间,返回 space_id 与名字。使用场景:要按知识库找文档时,先拿空间列表,再用 feishu_wiki_node(传 space_id)列出根节点。前置条件:应用需要被加入知识库(知识库设置 → 成员/应用),否则返回空列表——空列表不代表接口坏了,而是这个应用还没被加入任何知识库,需要在知识库设置里添加此应用。只读,不改知识库结构。

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

Input Schema

NameRequiredDescriptionDefault
limitNo最多返回多少个空间,默认 50,上限 50(超过按上限处理)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 「只读」 remark is partly redundant. What it does add is non-obvious operational semantics: an empty result means the app was never added to any wiki, not that the API failed, and the app must be granted membership in knowledge-base settings. That preempts a common misdiagnosis. It does not cover pagination behavior for the limit cap.

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-loads purpose, then usage scenario, then prerequisite, then safety hint — a sensible ordering with no filler sentences. Slightly repetitive in restating the empty-list point twice (「否则返回空列表」 and 「空列表不代表接口坏了」), but the emphasis is defensible for a failure mode that is easy to misread.

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

Completeness5/5

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

No output schema exists, and the description compensates by naming the returned fields (space_id 与名字). A single optional parameter tool with annotations plus the membership prerequisite and empty-list semantics is fully specified; nothing needed to call it correctly is missing.

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 description coverage is 100% and the single `limit` parameter already documents its default (50) and hard cap (50, values above are clamped) in Chinese. The description adds nothing about this parameter, so the schema does all the work and baseline 3 applies. It does describe the return fields, but that is not parameter semantics.

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?

Uses a specific verb and resource (列出 / 飞书知识库 wiki 空间) and adds the scoping qualifier 「机器人能看到的」, plus what is returned (space_id 与名字). It explicitly names the different sibling feishu_wiki_node and how it differs, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit ordered workflow: 「要按知识库找文档时,先拿空间列表,再用 feishu_wiki_node(传 space_id)列出根节点」, naming the alternative and the exact parameter to pass to it. It also states a prerequisite (app must be added to the wiki), which is the only when-not condition that matters for this tool.

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