Skip to main content
Glama

set_group_leave

Destructive

Leave a QQ group by passing its group ID, so an AI-operated QQ account can exit the target group after confirmation.

Instructions

退群 会退出该群,请确认目标群号后调用。

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversible nature is flagged in structured data. The description does add the useful clarification that the bot itself exits the group (not other members), but it says nothing about whether rejoining is possible, what permissions are needed, or what happens to the bot's session afterwards.

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?

Two short clauses, with the action front-loaded, so there is no wasted wording. The closing caution is borderline boilerplate, but it is justified for a destructive operation.

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 single-parameter destructive tool with annotations that cover its safety profile and no output schema, the definition is adequate but thin. It omits what a caller should expect after leaving and whether re-invitation is required, which are the details an agent would most want.

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?

Only one parameter, group_id, has full schema coverage with a description of 群号, so the schema is already sufficient. The description's instruction to confirm the target group number reinforces that this identifier must be verified before a destructive call, which is a small but real addition to the parameter's meaning.

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: 退群 (leave the group) and 会退出该群 (the bot exits that group). This clearly distinguishes the tool from sibling removal-style operations such as set_group_kick, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The only guidance is a caution to confirm the target group number before calling (请确认目标群号后调用), which is a precondition rather than when-to-use guidance. It does not say when leaving is appropriate versus kicking members or transferring ownership.

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