Skip to main content
Glama

set_group_member_permissions

Set or update a QQ group's member permissions, such as album uploads, temporary sessions, and creating groups, by changing only the specified permission fields; group owner access is required.

Instructions

设置群成员权限(仅群主可改) 至少传一个权限字段;仅修改传入的权限,其余保持原样。 Rules: at least one of: allow_member_upload_album, allow_member_temporary_session, allow_member_create_group.

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
allow_member_create_groupNo
allow_member_upload_albumNo
allow_member_temporary_sessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the bar is lower. The description still contributes real behavioral context the annotations cannot: changes require group-owner authorization, and the update is partial — only the supplied flags change while all others retain their current values. What is missing is whether the change is reversible or what the response reports.

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 compact sentences plus a rules clause, with the authorization caveat and the partial-update semantics front-loaded. The trailing 'Rules: at least one of...' restates the same three field names already listed, which is mildly redundant but useful as a hard constraint.

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 four-parameter mutation with annotations but no output schema, the definition covers the essentials: owner-only authorization, partial-update semantics, and the minimum-one-field rule. The remaining gap is the per-flag meaning, which neither the schema nor the description supplies.

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 only 25% — just group_id ('群号') is documented — so the description must compensate, and it partly does by enumerating the three permission flags and imposing the at-least-one constraint. It never explains what any individual flag actually grants, which is the main semantic gap given the low coverage.

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 (set group member permissions) and adds the ownership constraint '仅群主可改'. It does not explicitly distinguish itself from the closely named sibling set_group_admin_permissions, so the agent must infer the member-vs-admin split from the names alone.

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 implied rather than stated: the owner-only restriction and the 'at least one field' rule effectively define when the call can succeed. However, there is no explicit guidance on when to choose this over set_group_admin_permissions or the corresponding get_* tool, leaving the alternative selection to inference.

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