onebot11-mcp

set_group_admin

Set or revoke a group member's administrator rights by specifying group and user; use enable true to grant admin status or false to remove it.

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

Name	Required	Description
`enable`	No	true=设为管理员，false=取消，默认 true
`user_id`	Yes	目标成员的 QQ 号
`group_id`	Yes	目标群号。用 get_group_list 取真实值，别凭记忆填

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. '会改变对方在该群的权限' does disclose that this is a mutation of another user's privileges, but nothing is said about required permissions, reversibility, or failure modes for a privileged operation.

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 sentences, front-loaded with the action, with no filler. It is efficient, though extremely terse for a privileged mutation.

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?

A mutation tool with no annotations and no output schema should at minimum state the authorization prerequisite and any side effects on the target; the description only notes that permissions change, leaving an agent unable to predict errors or requirements.

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 description coverage is 100% and the schema itself documents all three parameters, including the enable default and the get_group_list hint for group_id. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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+resource pair: setting or unsetting group administrator, plus the effect (the target's permissions in that group change). It is clearly distinguishable from siblings like set_group_card or set_group_kick, though it never names or contrasts an alternative.

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?

Usage is only implied by the purpose; there is no statement of when to prefer this over set_group_special_title or other role tools, and no prerequisites (e.g. the caller must be group owner) are given.

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