Skip to main content
Glama

set_qzone_profile

Update the current QQ account's Qzone name or description, changing only the fields provided; use an empty string to clear a field and supply at least one field.

Instructions

修改当前账号的 QQ 空间名称或说明 仅修改提供的字段;空字符串表示清空对应字段。 Rules: at least one of: name, description.

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_qzone_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo新的空间名称,空字符串表示清空,省略则保留
descriptionNo新的空间说明,空字符串表示清空,省略则保留

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare non-read-only, non-destructive, open-world. The description adds meaningful behavior beyond that: partial-update semantics (unspecified fields are preserved) and the non-obvious fact that an empty string erases a field's content, which is effectively a soft destructive action the agent must be careful about.

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?

One compact sentence plus a rule line; the clearing semantics and the at-least-one constraint are front-loaded. There is mild duplication between '仅修改提供的字段' and the per-field schema text, but nothing wasteful.

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 two-parameter mutation with full schema coverage and annotations covering the safety profile, the description supplies the decision-relevant semantics (clear-vs-preserve, minimum one field) and needs no output explanation since no output schema exists. Nothing critical is missing.

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 100% and the per-parameter descriptions already explain empty-string-clears vs omitted-retains, so the description mostly restates those. It does add the cross-parameter constraint 'at least one of: name, description,' which the schema does not enforce (0 required, no minProperties), giving it real added value.

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+resource: modifying the current account's QQ Zone (空间) name or description, which is distinguishable from the main-profile sibling set_qq_profile and the read-only get_qzone_profile. It does not explicitly name an alternative, 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 Guidelines4/5

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

Gives clear operational rules: only supplied fields are changed, an empty string clears a field, and at least one of name/description must be provided. It does not state when to prefer this over other profile tools, but the mutation scope is unambiguous.

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