Skip to main content
Glama

set_group_admin

Grant or revoke QQ group administrator status for a member; requires group owner permission and updates the member's admin role.

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>",
      "user_id": "<user_id>"
    },
    "name": "set_group_admin"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableNo
user_idYesQQ 号
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the privilege requirement (group owner only) and the side effect (the target gains administrator identity). It does not explain failure modes or whether existing admin flags persist, but the key behavioral traits are surfaced.

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, front-loaded with the operation and followed by permission and effect. No filler or redundancy, though the punctuation could be clearer about separating the enable semantics.

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?

A mutation tool with no output schema and three parameters needs clear preconditions and side effects, and those are given. However, the enable default and the response behavior are not explained, leaving some gaps for a privileged write operation.

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%, with group_id and user_id documented in-schema; the enable boolean has a default of true but no description. The phrase 设置/取消 hints that the tool toggles the admin role, but the description never maps that idea to enable, so meaning is mostly left to the schema.

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?

The description names a specific verb and resource, namely setting or unsetting group administrator, and states that it grants the member the administrator role. It does not distinguish the tool from siblings such as set_group_admin_permissions or get_group_admin_settings, but the core operation is unambiguous.

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?

It states that group owner permission is required, which is useful preconditions guidance. It does not say when to prefer this over admin-permission siblings, nor what happens when the caller is not the owner or the target is not a member.

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