Skip to main content
Glama

set_friend_remark

Set or update a QQ friend's remark name by user ID to organize contacts and identify them clearly.

Instructions

设置好友备注

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": {
      "user_id": "<user_id>",
      "remark": "<remark>"
    },
    "name": "set_friend_remark"
  }
}

Input Schema

NameRequiredDescriptionDefault
remarkYes
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/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/network profile is known. The description adds nothing: it does not say what happens to an existing remark, whether an empty remark clears it, whether the target must be a friend, or what errors to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A four-character phrase is free of padding but is under-specified rather than concise; there is no structure, no front-loaded scope, and no information an agent could act on beyond the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 zero schema coverage, the description is far too thin: it omits permission requirements, remark-clearing behavior, and any return or error semantics.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It only hints that a 'remark' exists; it never explains that user_id identifies the target friend (integer or string), that it is a minimum-1 ID, or what value format remark accepts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"设置好友备注" merely restates the tool name in Chinese; it names the resource (好友) and the field (备注) but adds no verb detail, scope, or differentiation from set_group_remark beyond the word 'friend'.

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 when-to-use guidance, no mention of prerequisites (e.g. the user must be a friend), and no reference to alternatives such as set_group_remark for group contexts. The agent must infer usage entirely from 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