Skip to main content
Glama

机器人所在的会话

feishu_chats
Read-only

Lists all Feishu group and direct conversations the bot belongs to, returning chat IDs and names so agents can pick the right target before sending messages or reading history.

Instructions

列出机器人当前所在的所有会话(群 + 单聊),返回 chat_id 与名字,供后续发送/读历史时当 target 用。只返回文本,不会往飞书里发任何消息,所以可以放心在探索阶段调用。不确定"该往哪个群发"、或者需要 chat_id 但手上只有群名时,先调这个。人数只在飞书真的返回了 member_count 时才显示;需要确切成员名单请改用 feishu_members。with_members=true 会额外对每个群发一次成员请求(前 5 个名字),会话多时会明显变慢。

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_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo最多返回多少个会话,默认 20,上限 100(超过按 100 处理)。
with_membersNo是否额外拉取每个群的成员名字(各取前 5 个),默认 false。为 true 时对每个群多发一次 listMembers 请求。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that the tool only returns text and never posts into Feishu, making it safe during exploration. It also warns that with_members=true issues an extra listMembers request per group and noticeably slows down with many chats, and that member_count appears only when Feishu actually returns it. What's missing is anything about ordering or result completeness, but the behavioral picture is substantially better than the annotations alone.

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 content is front-loaded with purpose and read-only reassurance, then conditional caveats, which is the right order for an exploration tool. A few clauses are slightly repetitive (the safety point and the 'call this first' advice overlap), but no sentence is wasted.

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?

For a two-parameter list tool with full schema coverage and no output schema, the description covers purpose, return fields, safety, cost of the optional parameter, and the fallback sibling. Nothing an agent needs to select or invoke it correctly is absent.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: with_members costs one extra request per group and returns only the first 5 member names each, and it steers the agent to feishu_members when an exact roster is needed. The limit parameter's default and cap are left to the schema, which is acceptable given full coverage.

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 gives a specific verb and resource ('列出机器人当前所在的所有会话(群 + 单聊)'), states the scope (chats the bot is in), and names the returned fields (chat_id 与名字). It also clarifies the downstream purpose (act as a target for sending or reading history), which distinguishes it from messaging siblings at a glance.

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?

It explicitly says when to call it ('不确定该往哪个群发、或者需要 chat_id 但手上只有群名时,先调这个') and names the alternative for the adjacent need ('需要确切成员名单请改用 feishu_members'). Both the trigger condition and the sibling routing are spelled out, not inferred.

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