Skip to main content
Glama

set_group_remark

Assign a custom remark to a QQ group using its group ID, helping users label and identify groups within their own QQ account.

Instructions

设置群备注 将 group_id 替换为当前账号可访问的群号。

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

Input Schema

NameRequiredDescriptionDefault
remarkYes
group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds nothing beyond that: it does not say whether an empty remark clears the value, whether the change is visible to other members, or what permissions are required.

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 sentences with no filler, and the core action is front-loaded. The second sentence is a slightly awkward template-style hint but is brief enough not to feel wasteful.

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 two-parameter mutation with no output schema and no parameter documentation in the schema, the description is thin. It never addresses permissions, overwrite semantics, or the effect of the call, so an agent still has to guess at the important behaviour.

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 0%, so the description must compensate. It does add a real constraint on group_id (must be a group number the current account can access), but leaves the remark parameter completely unexplained and never says whether it overwrites or clears an existing remark.

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 (set group remark), which is enough to distinguish it from most siblings, and it stays concrete rather than restating the name. It stops short of clarifying how it differs from near neighbours like set_group_card or set_friend_remark.

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?

There is no statement of when to use this instead of an alternative, nor any prerequisites such as needing to be a group member or admin. The only guidance is a note about substituting an accessible group ID, which is a templating instruction rather than usage context.

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