Skip to main content
Glama

set_group_kick

Destructive

Kick a specified member from a QQ group by providing the group ID and member QQ number; success depends on your account’s permissions 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>",
      "user_id": "<user_id>"
    },
    "name": "set_group_kick"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesQQ 号
group_idYes群号
reject_add_requestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructive=true, readOnly=false and openWorld=true, so the description only needs to add context. It does add the permission-dependency caveat, which is genuinely useful, but says nothing about irreversibility or what reject_add_request does to the kicked member's ability to rejoin.

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?

Short and front-loaded, but '替换' (replace) is misleading wording for supplying an identifier and costs the agent a moment of parsing. The permission caveat is worth its space.

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 destructive, no-output-schema mutation, the definition covers who can act but omits the consequences of acting: what happens to the member, and the effect of reject_add_request. Adequate but with clear gaps an agent would want filled.

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 coverage is 67% and the description only loosely maps group_id and user_id ('替换群号和成员 QQ 号'), adding nothing beyond the schema's own labels. The third parameter reject_add_request is unexplained in both schema and description.

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 ('踢出群成员' - kick a group member) and names the two identifying inputs. It does not distinguish itself from the sibling set_group_kick_members (batch variant) or set_group_ban, so an agent cannot tell from the text alone which removal tool to pick.

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 only guidance is a permission prerequisite ('操作是否允许取决于当前账号在该群的权限'). There is no statement of when to use this versus set_group_kick_members or set_group_ban, and no note on when kicking is inappropriate.

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