Skip to main content
Glama

set_group_portrait

Sets a QQ group portrait using a server-readable image file, with the target group specified by its group ID.

Instructions

设置群头像 示例路径位于 SnowLuma 服务端,须替换为该服务可读取的实际文件。

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>",
      "file": "<file>"
    },
    "name": "set_group_portrait"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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. The description adds one real behavioral fact: the file must be a path the SnowLuma service itself can read, and the sample path must be substituted. It still omits permission requirements, format/size limits, and that the previous avatar is replaced.

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, front-loaded with the purpose and followed by the one caveat that matters. The mention of the specific SnowLuma example path is slightly implementation-flavored but earns its place as a warning against copying a placeholder.

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 and openWorldHint=true, the description covers the oddest parameter well but leaves out required permissions, image constraints, overwrite behavior, and any failure modes. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (only group_id is described), so the description carries weight for 'file'. It explains that this is a server-side readable path rather than a URL or uploaded blob, which meaningfully constrains how to fill the parameter and is not in the schema.

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 opening phrase '设置群头像' states a specific verb and resource, so an agent can tell this sets a group's avatar rather than a name, card, or remark. It does not distinguish itself from other set_group_* mutations beyond the action name, but the action itself is unambiguous.

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 tool versus alternatives, no prerequisite such as bot admin rights in the group, and no note that it overwrites any existing avatar. Usage is only implied by the name.

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