Skip to main content
Glama

set_qq_avatar

Set a QQ account avatar by providing a file path accessible to the server.

Instructions

设置 QQ 头像 示例路径位于 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": {
      "file": "<file>"
    },
    "name": "set_qq_avatar"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes

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 mutation and openness profile is covered. The description adds genuinely new behavior: the path refers to a file on the SnowLuma server side and must be readable by that service, implying a server-local filesystem dependency rather than a client upload. It says nothing about what happens on failure, supported formats, or whether 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 with the purpose front-loaded and no filler. The second sentence is slightly awkward but each clause carries information about the path constraint.

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 one-parameter mutation tool with no output schema, the definition covers purpose and the key server-side path constraint. It leaves out image format/size expectations and error behavior, which an agent would want before invoking a destructive-adjacent avatar change.

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% for the single required "file" parameter, so the description must carry the meaning — and it does add real semantics by clarifying that the value is a server-side path readable by SnowLuma, not a URL or local client path. It stops short of giving a concrete accepted path format, example, or any size/type constraints, so the gap is only partially filled.

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?

"设置 QQ 头像" gives a specific verb (set) and resource (QQ avatar), so the agent knows exactly what the tool does. It does not distinguish itself from nearby siblings such as set_qq_profile or set_group_portrait, which also involve profile imagery, so differentiation is left to the names alone.

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, and no prerequisites or exclusions are given. The only guidance is a path caveat, which is operational rather than usage-selection 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