Skip to main content
Glama

set_group_whole_ban

Destructive

Enable or disable whole-group mute for a QQ group to restrict all members from speaking; permission depends on the account's role in that group.

Instructions

全员禁言开关 替换群号和成员 QQ 号;操作是否允许取决于当前账号在该群的权限。

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": {
      "group_id": "<group_id>"
    },
    "name": "set_group_whole_ban"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableNo
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false. The description adds genuine behavioral context by stating the operation is gated on the caller's permissions in that group, which is not in the annotations. It does not explain what state changes occur (e.g. that disabling re-enables speech) or the blast radius of muting every member.

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

Conciseness3/5

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

It is short and front-loads the core purpose in the first clause. But the second clause about replacing group and member QQ numbers is wasted, misleading boilerplate that does not earn its place.

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

Completeness2/5

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

For a destructive, permission-gated mutation with no output schema and only half the parameters documented, the description leaves key gaps: the semantics of enable=false, the scope of the ban, and any confirmation of the resulting state. The permission note helps, but the inaccurate parameter mention further undermines completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: group_id is documented as '群号' in the schema, while enable (default true) has no description anywhere. The description does not clarify that enable=true turns the mute on and false lifts it; worse, it references a '成员 QQ 号' parameter that does not exist in the schema, actively confusing the parameter model.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening phrase '全员禁言开关' (whole-group mute switch) names a clear resource and action, so the core purpose is identifiable. However, the following clause '替换群号和成员 QQ 号' is garbled boilerplate that mentions a member QQ parameter the tool does not have, and nothing distinguishes it from the sibling set_group_ban.

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?

The description notes that whether the operation is permitted depends on the account's permissions in the group, which is a useful prerequisite. But it gives no guidance on when to use this whole-group toggle versus the per-member set_group_ban sibling, and no exclusion or condition for choosing between them.

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

Deploy Server

Other Tools