Skip to main content
Glama

set_group_admin_permissions

Configure an existing QQ group admin's message-recall and member-removal permissions, including daily removal limits, without granting or changing the admin role.

Instructions

设置指定管理员的撤回和移除成员权限 需要当前账号具有修改权限;不会授予管理员角色。仅修改显式字段。开启移除必须提供上限,0 表示不限;修改上限需同时传 kick_member=true。 Rules: at least one of: recall_member_message, kick_member; kick_member=true requires kick_member_per_day: 0, 5, 10, 20, 50, 100 or 200; kick_member_per_day requires kick_member=true.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesQQ 号
group_idYes群号
kick_memberNo
kick_member_per_dayNo
recall_member_messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false and openWorld=true; the description goes further by disclosing the authorization requirement, that no admin role is granted, that unspecified fields are left untouched, and that enabling removal requires a quota where 0 means unlimited. These are non-obvious behavioral facts an agent could not derive from the structured data, though the effect on already-set values is not described.

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 definition is dense but front-loaded: purpose, then precondition, then constraints, then a formal Rules block. Nothing is redundant, though the mixed prose-plus-rules structure restates the kick_member/kick_member_per_day dependency twice, which costs some tightness.

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 5-parameter mutation tool with no output schema and 40% schema coverage, the description supplies the authorization model, the mutation scope, the cross-field constraints and the quota semantics an agent needs to call it correctly. Only the return/confirmation behavior is unaddressed, which is a minor gap given the tool's simplicity.

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 only 40%, so the description must compensate, and it does: it defines the kick_member_per_day quota semantics (0 = unlimited), enumerates the permitted values 0/5/10/20/50/100/200 that the schema only bounds as 0-200, and spells out the bidirectional dependency between kick_member and kick_member_per_day. The remaining params group_id and user_id are left to the schema, which already labels them as 群号 and QQ 号.

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 names a specific verb and resource ('设置指定管理员的撤回和移除成员权限') and immediately bounds the scope with '不会授予管理员角色', which separates it from set_group_admin. It also scopes the change to explicitly-passed fields ('仅修改显式字段'), so an agent can distinguish it from the read-side sibling get_group_admin_permissions without opening a schema.

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?

It states the precondition ('需要当前账号具有修改权限') and the invocation constraint that at least one of recall_member_message or kick_member must be supplied, which is real when-to-use guidance. It stops short of naming get_group_admin_permissions as the read alternative, so the alternative routing is implied rather than explicit.

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