Skip to main content
Glama

get_group_admin_permissions

Read-only

Retrieve a QQ group administrator's permissions, including recall, member removal, daily removal limits, and join-verification message reception, using a group ID and admin QQ number.

Instructions

读取指定管理员的撤回、移除成员、每日移除上限及接收验证消息状态 user_id 为目标管理员 QQ 号;包含接收加群验证消息状态。 Returns: 服务器返回的管理员权限;未返回或未指定的开关为 null。每日上限仅在移除权限开启时返回,0 表示不限。

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": "get_group_admin_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description goes beyond them with real return-shape behavior: unspecified or unreturned switches come back as null, the daily removal limit is only populated when removal permission is enabled, and 0 means unlimited. Gaps remain around failure modes (invalid group/user_id) and whether openWorldHint implies remote fetch latency.

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?

Purpose and parameters are front-loaded, which is good, but the receive-verification status is stated twice (once inside the enumeration and again in '包含接收加群验证消息状态'), and the mixed Chinese/English 'Returns:' clause makes the text bumpier than needed. Nothing is fatally wasteful, but the redundancy costs it a point.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so reasonably: it names the four permission flags and specifies null/conditional/zero semantics. For a two-parameter read tool that is close to complete; only error behavior and admin-existence preconditions are left unaddressed.

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 100% — both group_id (群号) and user_id (QQ 号) are documented in the schema. The description only adds a modest clarification that user_id is the target admin's QQ number, which usefully disambiguates the role of that parameter but is close to what the schema already says.

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 opens with a concrete verb (读取) and resource (管理员权限) and enumerates the exact permissions exposed: 撤回, 移除成员, 每日移除上限, 接收验证消息状态. This lets an agent tell it reads one admin's permission flags rather than group-wide settings. It never names the obvious counterpart set_group_admin_permissions, so sibling differentiation is only implied by the 'get' prefix.

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: the agent can infer this is the read path for an individual admin's permission flags, contrasted against the set_* siblings. There is no explicit 'use this when…, not that' guidance, no mention of prerequisites such as the user actually being an admin, and no statement about what happens for non-admin users.

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