Skip to main content
Glama

add_group_tag

Adds a profile tag to a specified QQ group category and sets the category and tag; requires current account admin permissions.

Instructions

向某个群分类添加资料标签 替换实际群分类和标签;需要当前账号有管理权限。

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_class": "<group_class>",
      "name": "<name>"
    },
    "name": "add_group_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
group_classYes

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 mutating, network-facing nature is covered structurally. The description adds valuable behavioral context by disclosing the admin-permission requirement, but the word '替换' (replace) sits uneasily with destructiveHint=false and the description never clarifies whether existing tags are lost, which is exactly the detail an agent needs before calling.

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 definition is short and the permission requirement is placed last, but the add-versus-replace tension makes the single main clause hard to act on. Length is not the problem; the wording is ambiguous rather than wasteful.

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 two-parameter mutation with no output schema, the description covers the essentials: it identifies the subject, the mutation, and the admin-permission prerequisite needed to call it correctly.

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?

Schema description coverage is 0% and neither of the two parameters is explained: the description does not say whether group_class is a classification node ID or a numeric type, nor whether name is the tag's display name or an identifier. With no schema documentation to fall back on, the description should have carried this meaning but does not.

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 description names a verb and resource (add a tag to a group classification) but immediately undercuts itself with '替换实际群分类和标签' (replace the actual group classification and tag), so an agent cannot tell whether this creates a new tag or overwrites existing ones. It does not distinguish this from the sibling delete_group_tag beyond the add/delete verb.

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 usage guidance is the prerequisite that the current account needs admin permission, which is useful but not a when-to-use rule. There is no statement of when to prefer this over delete_group_tag or other group-setting tools, and no information about failure behavior when the permission is absent.

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