Skip to main content
Glama

set_group_member_invite_policy

Set a QQ group's member invitation policy to disabled, require approval, no approval, or no approval under 100 members; the account's group permissions determine whether the change is allowed.

Instructions

设置群成员邀请策略 替换群号和成员 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>",
      "policy": "<policy>"
    },
    "name": "set_group_member_invite_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYes
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful context that authorization depends on the caller's role in the group, which goes beyond the annotations. But it discloses nothing about what changes when the policy is applied or the effect on existing members.

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?

The description is short and the purpose statement comes first. The second sentence contains the permission note usefully bundled with a nonsensical '替换群号和成员 QQ 号' fragment that reads like leftover template text and undermines clarity.

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?

This is a mutation tool with no output schema; the most important missing element is what each policy value means and what happens to pending or existing invites. The dangling reference to a nonexistent member parameter adds to rather than resolves the confusion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage, the description needs to help resolve parameters, but it instead mentions a '成员 QQ 号' that does not exist in the schema, which is actively misleading. It also leaves the four policy enum values (especially 'no_approval_under_100') completely unexplained.

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 ('设置群成员邀请策略'), which tells an agent what is being changed. However, it never differentiates this from siblings such as set_group_add_option or set_group_add_request, and it adds a confusing clause about '成员 QQ 号' even though no such parameter exists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is that the operation's success depends on the current account's permissions in that group; this is a prerequisite, not a rule for when to use this tool versus alternatives. It gives no rule for when to choose this tool versus the multiple other group-setting siblings.

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