Skip to main content
Glama

set_qq_profile

Updates the current QQ account profile by changing only the specified fields, such as nickname, sex, or personal note.

Instructions

设置 QQ 资料 会修改当前账号的资料;只传入需要修改的字段。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_qq_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNo0 未知,1 男,2 女
nicknameNo
personal_noteNo

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?

The annotations already declare that this is not read-only, not destructive, and open-world; the description adds the important fact that the write targets the current account's own profile and that unspecified fields are left untouched. It does not say whether the client must be online, whether the change can be reverted, or what happens on invalid values.

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 compact clauses with no filler; the mutation scope comes first and the parameter rule second. It is appropriately sized for a three-parameter setter and has nothing that should be trimmed.

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 simple setter with annotations and no output schema, this covers the essentials. What is missing is operational context: prerequisites (logged-in client), failure modes, and confirmation that unlisted fields are preserved.

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 description coverage is only 33%: sex carries an inline enum description (0 unknown, 1 male, 2 female), but nickname and personal_note carry no schema text. The description's partial-update rule applies to all three parameters, but it gives no field-level semantics such as nickname length limits, whether an empty string clears the note, or whether QQ enforces server-side validation, so it only partly makes up for the thin 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?

States a specific verb-plus-resource: it sets QQ profile fields on the currently logged-in account. That scope note ('会修改当前账号的资料') distinguishes it from the sibling set_qzone_profile, though the description never names that sibling explicitly.

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?

Conveys a partial-update contract — pass only the fields you want changed — which is real usage guidance for calling the tool. It offers no guidance on when to choose it over set_qzone_profile, set_qq_avatar, or set_diy_online_status, so the agent must infer the boundaries from the names alone.

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