Skip to main content
Glama

set_group_card

Set or clear a QQ group member's group card by specifying the group ID and user ID. Use it to update group nicknames, subject to 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_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardNo
user_idYesQQ 号
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safety profile is covered. The description adds two genuine pieces of context beyond that: an empty string clears the card, and success depends on the calling account's permissions in that group. It omits idempotency and error behaviour, so a 3 rather than higher.

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 clearing behaviour front-loaded in the parenthetical. The middle clause about group and member QQ numbers is the only part that does not clearly earn its place.

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 3-parameter mutation with no output schema, the description covers the target resource, the non-obvious empty-string clearing rule, and the permission dependency. It could say more about failure behaviour or required privilege level, but nothing essential to calling it correctly is missing.

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%; group_id and user_id already carry '群号' and 'QQ 号' descriptions, while the undocumented card parameter is the one the description explains via '空字符串清除'. However, the sentence '替换群号和成员 QQ 号' is vague and adds little usable meaning about how the target is identified.

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 and resource (设置群名片 / set group member card) plus the clearing semantics, so the operation is identifiable without the schema. It does not explicitly distinguish itself from adjacent siblings such as set_group_remark or set_group_name, which is the only clarity gap.

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 description gives no when-to-use or when-not-to-use guidance and names no alternatives. The only conditional statement concerns permission to perform the operation, which is a runtime constraint rather than routing guidance.

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