Skip to main content
Glama

qzone_board_reply

Replies to a specific QQ Zone message board post using its message ID and provided content, letting you answer board messages from your account.

Instructions

Reply to a message on a 留言板 (usually your own).

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": {
      "message_id": "<message_id>",
      "content": "<content>"
    },
    "name": "qzone_board_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinNoQQ number whose 空间 to use (default: your own)
contentYesReply text
message_idYes留言 id from qzone_board_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 write nature is known. The description adds essentially nothing beyond that — no note on permissions, whether the reply is publicly visible, whether it can be edited/undone, or what a successful reply yields.

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?

A single front-loaded sentence with no wasted words. Its brevity is efficient, though it leans on being terse rather than richly informative.

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 mutation tool with three parameters and no output schema, the definition should say more about effects and visibility of the reply. The parameter layer is fully covered by the schema, but the behavioral picture an agent needs before writing publicly visible content is absent.

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 100%, with all three parameters documented including the uin default and the pointer to qzone_board_list for message_id. The description adds only the 'usually your own' nuance on uin, which the schema already states, so this is baseline territory.

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 ('Reply to a message on a 留言板') and adds a scope hint ('usually your own'), which is clearer than a bare restatement of the name. It stops short of differentiating this from nearby siblings such as reply_to_message or comment_qzone, so an agent cannot fully disambiguate from the text alone.

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?

'usually your own' hints at the typical board context but is about scope, not when-to-use. There is no statement of prerequisites, no exclusion of alternative reply/comment tools, and no guidance on when this tool is wrong to pick.

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