Skip to main content
Glama

set_group_admin_receive_verify

Sets whether a specified QQ group admin receives join-verification messages, independent of recall and member-removal permissions.

Instructions

设置指定管理员是否接收加群验证消息 user_id 为目标管理员 QQ 号;需要当前账号具有修改权限。独立于撤回和移除成员权限。

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>",
      "enable": "<enable>"
    },
    "name": "set_group_admin_receive_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableYes
user_idYesQQ 号
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description supplies the permission requirement and explicitly scopes the change as independent from other admin privileges, which is genuinely additive context for a toggling mutation. It does not discuss reversibility guarantees or the response, but the annotations already signal a non-destructive write.

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?

Three compact semicolon-separated clauses, front-loaded with the action before the parameter note and the permission note. No filler, though the permission-independence clause is somewhat terse.

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 three-parameter boolean toggle with no output schema, the description covers purpose, the key parameter identity, and the authorization requirement. Only the semantics of the undocumented `enable` field and any error/pagination behavior are left implicit.

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 67%, with group_id and user_id already labeled as group number and QQ number. The description adds that user_id must be the target *admin's* QQ number and frames enable as the receive-or-not flag, clarifying meaning the schema does not.

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 specific verb+resource: toggling whether a designated admin receives group-join verification messages. That is clearly distinct from sibling operations like set_group_admin (admin status) or set_group_admin_permissions, though it never names an alternative tool 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?

It states a real precondition — the calling account must hold modification permission — and notes independence from recall/remove-member permissions, which helps an agent decide feasibility. It stops short of saying when to prefer this tool over nearby admin-permission tools or when not to use it.

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