Skip to main content
Glama

set_group_robot_add_option

Configures a QQ group robot's add/join options by setting member switch and review flags for a specified group, subject to the account's group permissions.

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
robot_member_switchNo
robot_member_examineNo

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 the operation is mutating (readOnlyHint false), non-destructive, and open-world. The description adds the important auth constraint that success depends on the account's permissions in the group, but it does not explain the effect of robot_member_switch or robot_member_examine, and the 'replace group number/member QQ' phrasing is confusing rather than clarifying.

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 front-loads the purpose, but the second clause is confusing and appears to reference parameters that do not exist, reducing clarity. It is concise but not fully well-formed.

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?

For a mutating tool with three parameters, one required and low schema coverage, the definition should explain what the two robot-member switches do and what changes they cause. Instead it only states a permission caveat, leaving the core option semantics unresolved.

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?

Only group_id is documented in the schema (33% coverage); robot_member_switch and robot_member_examine have no descriptions. The description mentions group number but says nothing about the two switch parameters, so it does not compensate for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause names a specific verb and resource ('设置群机器人加群选项'), but the follow-up '替换群号和成员 QQ 号' does not match the schema and muddies what is actually being set. It also does not distinguish this robot-specific option from the sibling set_group_add_option.

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?

The only usage guidance is the permission prerequisite ('操作是否允许取决于当前账号在该群的权限'), which is useful context but does not say when to choose this tool over set_group_add_option or when the operation should be avoided. No alternatives or exclusions are named.

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