Skip to main content
Glama

add_custom_face

Adds a custom face emoji to a QQ account’s favorites using an image file path readable by the server.

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

Input Schema

NameRequiredDescriptionDefault
fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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/safety profile is covered. The description adds real value by revealing that the file argument is a path on the SnowLuma server rather than a local upload, but it says nothing about failure modes, duplicates, or whether the added face is returned.

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 the parameter caveat second; nothing is redundant. The phrase "示例路径位于 SnowLuma 服务端" is slightly compressed and could be clearer, but it does not waste space.

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 one-parameter mutation with no output schema, the description covers the two things an agent needs: the operation and how to supply the file correctly. It is thin on post-call behavior (return value, duplicate handling), which keeps it from a 5.

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 0% and the schema only says the single `file` param is a non-empty string, so the description carries the burden. It does exactly that: it explains the value must be a server-readable path and that the sample path must be substituted, which prevents the most likely invocation error (passing a local or client-side path).

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 (add) plus resource (custom/favorite face), so an agent can identify the operation immediately. It does not differentiate itself from siblings such as modify_custom_face or send_custom_face, so it stops short of a 5.

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 versus modify_custom_face, move_custom_face_to_front, or send_custom_face, and no prerequisites (e.g. whether the face must already exist, whether duplicates are rejected). Usage is only inferable from the verb 'add'.

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