Skip to main content
Glama

set_group_special_title

Set or update a QQ group member's special title using group ID, user ID, and optional title text; the operation depends on the account's permissions in that group.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesQQ 号
group_idYes群号
special_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the operation's direction and safety profile are supplied by structured data. The description adds real context beyond those annotations: that authorization depends on the caller's permissions in the group, and that the title string substitutes the group number and member QQ number. It does not say what an empty default title does (presumably clearing the title) or what the response contains.

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 short clauses, front-loaded on the operation, with no wasted wording. The second clause is compressed enough that the placeholder semantics read as ambiguous rather than economical.

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 three-parameter mutation tool with no output schema and no annotations that cover mutation semantics, the description covers permissions and title substitution but leaves the empty-title default and the resulting state undefined. It is adequate but leaves a real gap for an agent deciding how to call it.

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 67%, and the schema already documents user_id and group_id, leaving special_title with no schema description. The description partly compensates by explaining that the title text substitutes the group number and member QQ number, but the phrasing ('替换群号和成员 QQ 号') is ambiguous about whether this is placeholder syntax or an automatic substitution, and it does not explain the empty-string default.

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?

States a specific verb+resource ('设置群头衔' / set group special title), which is unambiguous on its own. It does not distinguish itself from neighboring tools such as set_group_card or set_group_name, so an agent must rely on the name alone to choose between similar group-setting siblings.

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 description notes that success depends on the current account's permissions in the group, which is a useful prerequisite. However, it gives no explicit when-to-use or when-not-to-use guidance and does not name which alternative tool to use for related operations such as member cards or group names.

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