Skip to main content
Glama

set_group_name

Sets a QQ group’s name from its group ID and an optional new name, replacing the group number and member QQ numbers; the account must have permission to change the group name.

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_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
group_nameNo

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 cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description still adds two pieces of behavioral context not in structured fields: that the supplied name undergoes placeholder substitution of the group number and member QQ numbers, and that the call may be rejected based on the account's permissions in that group. It does not say what the failure mode looks like (error vs silent no-op) when permissions are insufficient.

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 clauses with the operation front-loaded and the permission caveat second, no filler. The placeholder clause is dense and slightly telegraphic, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the description covers the key behaviors (permission gating, template substitution) but omits the effect of an empty group_name and the outcome on permission failure. These gaps matter for a rename operation where a caller could accidentally blank a group name.

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 50%: group_id is documented ('群号') while group_name carries only a default of empty string. The description partially compensates by explaining what group_name content may contain (placeholders replaced by group number and member QQ numbers), but it never clarifies whether the empty-string default means clearing the group name, which is the most consequential ambiguity for a caller.

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 the specific verb+resource pair '设置群名', which unambiguously identifies the operation. It does not distinguish itself from nearby siblings such as set_group_card or set_group_remark, which also alter group-visible naming fields, so the agent must infer the difference 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?

It states a precondition ('操作是否允许取决于当前账号在该群的权限'), which tells the agent success is permission-dependent, but gives no when-to-use vs when-to-use-another-tool guidance. No alternative is named for renaming a member's display name versus the group itself.

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