Skip to main content
Glama

set_qzone_ban

Blocks or unblocks a specified QQ user in the bot account's QQ Zone blacklist, enabling moderation of who can interact with that Qzone.

Instructions

拉黑或解除拉黑某人(修改机器人自身 QQ 空间黑名单;enable=true 拉黑,false 解除) 修改当前账号空间黑名单。

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>"
    },
    "name": "set_qzone_ban"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableNotrue 拉黑,false 解除拉黑
user_idYes目标 QQ 号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly given. The description adds real scope context by clarifying that only the bot's own Qzone blacklist is touched, but it says nothing about reversibility beyond the enable flag, error behavior for users not on the list, or whether existing content visibility changes.

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

Conciseness3/5

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

The core clause is front-loaded and short, but the closing sentence '修改当前账号空间黑名单' merely repeats the parenthetical's content, and '自身' vs '当前账号' introduces minor terminological drift. One of the two sentences does not earn its place.

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, fully documented, annotation-covered toggle with no output schema, the description covers purpose, scope and mode semantics adequately. Remaining gaps (idempotency, failure cases) are minor for a tool of this simplicity.

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%, so the baseline is 3; the description goes slightly beyond by restating the boolean polarity in plain language next to the action itself, making the default=true 'ban' direction unambiguous. It adds nothing about the user_id format beyond the schema's '目标 QQ 号'.

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

Purpose5/5

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

The description names a specific verb pair (拉黑/解除拉黑) and a precise resource (机器人自身 QQ 空间黑名单), and the scope qualifier '机器人自身/当前账号' separates it from account-agnostic siblings such as set_group_ban. An agent can determine what is being modified without opening the schema.

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?

It states the effect of enable=true vs false, which implies when each mode applies, but never names an alternative tool or an explicit precondition (e.g. must the target be a friend or a Qzone visitor). Usage is inferable but not spelled out.

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