Skip to main content
Glama

set_friends_category

Move a QQ friend into a chosen friends category by specifying either a category ID or an exact category name. Use it to reorganize contact groups through an AI assistant.

Instructions

移动好友到指定分组 categoryId 与 categoryName 二选一。 Rules: exactly one of: categoryId | categoryName. Returns: 成功时返回空数据。

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": {
      "uin": "<uin>"
    },
    "name": "set_friends_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinYes要移动的好友 QQ 号
categoryIdNo目标分组 ID
categoryNameNo目标分组名称(必须唯一且完全匹配)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 known. The description adds that a successful call returns empty data ('成功时返回空数据'), which is valuable because there is no output schema. It does not disclose failure behavior, such as what happens when categoryName is ambiguous or the friend is already in the target category.

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?

The description is short and front-loads the action before the rules. However, the 'categoryId 与 categoryName 二选一' clause and the English 'exactly one of: categoryId | categoryName' line restate the same constraint twice, which is mild redundancy rather than added clarity.

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 simple three-parameter mutation with full schema coverage and supplied annotations, the description covers the action, the key mutual-exclusivity rule, and the success return value. What remains missing is error and edge-case behavior, which is a modest gap for a tool of this complexity.

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?

With 100% schema coverage, the baseline is 3, but the description adds meaning the schema cannot express: categoryId and categoryName are mutually exclusive and exactly one is required. The JSON schema only marks uin as required and permits additional properties, so this XOR constraint is genuinely new information.

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: '移动好友到指定分组' (move friend to a designated category). This clearly separates it from read-oriented siblings such as get_friends_with_category. It stops short of explicitly naming an alternative tool, so it earns a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is a parameter-selection rule: 'exactly one of: categoryId | categoryName'. There is no statement of when to use this tool versus siblings, no prerequisites, and no mention of what happens if the friend or category does not exist. The mutual-exclusivity rule is useful but is invocation guidance, not tool-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