Skip to main content
Glama

解散一个群

feishu_chat_dissolve
Destructive

Dissolve a Feishu group chat permanently; the bot must be the group owner. Requires the chat ID and exact group name confirmation to prevent deleting the wrong group.

Instructions

解散群。不可撤销:群和群里的消息都会消失,机器人必须是群主。执行前先跟人确认一遍群名和群 id。

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": {
      "chat_id": "<chat_id>",
      "confirm": "<confirm>"
    },
    "name": "feishu_chat_dissolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes群 id(oc_ 开头)。
confirmYes把群名原样抄一遍作为确认(防止手滑删错群)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly given; the description still adds substantive context beyond them: irreversibility, that messages are destroyed along with the group, and the owner-permission requirement. It does not say what happens on a permission failure or how the call reports success, but the destructive semantics are well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, with the irreversible consequence front-loaded in bold and the precondition following. Every clause carries operational weight; nothing is repeated from the schema verbatim.

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 two-parameter destructive tool with full schema coverage and clear annotations, this covers purpose, danger, permissions, and the required pre-flight confirmation. Only failure modes and post-call state reporting are left implicit, which is acceptable since no output schema exists.

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% and both parameters are documented (chat_id prefix 'oc_', confirm as a verbatim group-name copy). The description adds procedural meaning by tying the confirm value to a human cross-check of both the group name and id, which is more than the schema's 'prevent mis-deletion' note alone.

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 ('解散群') with immediate scope: the group AND its messages disappear. No sibling in the list performs dissolution (feishu_chat_update is the nearest neighbor), so there is little ambiguity to dispel, but the definition never explicitly contrasts itself with update/leave-type operations.

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?

Gives a hard precondition ('机器人必须是群主') and a procedural rule ('执行前先跟人确认一遍群名和群 id'), which is exactly the when-to-use context an agent needs before an irreversible action. It stops short of naming an alternative (e.g., leaving a group vs dissolving it) or stating when not to use it.

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