Skip to main content
Glama

qzone_board_post

Posts a message to a QQ Zone message board (留言板) for a specified QQ number or your own account. Provide the target QQ number and message text to publish the entry.

Instructions

Write a message on someone's 留言板 (or 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": {
      "uin": "<uin>",
      "content": "<content>"
    },
    "name": "qzone_board_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinYesWhose 留言板 (QQ number)
contentYesMessage text

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 and network characteristics are covered by structured data. The description adds only that the target board can be your own, without disclosing visibility of the post, permission or friend-relationship requirements, rate limits, or whether the message can be removed later via qzone_board_delete.

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?

It is a single front-loaded sentence with no filler or redundancy. The brevity is efficient, though it borders on under-specification rather than maximal tightness.

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 write tool with no output schema, the description says nothing about what happens after posting, what is returned, or any constraints on the content. Annotations cover the safety profile, but an agent would still lack any indication of success behavior or permission requirements.

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 coverage is 100%, so both parameters are already documented in the schema, setting the baseline at 3. The description adds a marginal clarification that 'uin' can point at your own QQ number, but supplies no format detail (numeric vs string) beyond what the schema already states.

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 states a specific verb and resource: write a message onto a 留言板. It also clarifies that the board may belong to another user or to yourself, which tells an agent this is a content-creation action. It does not explicitly differentiate itself from siblings such as qzone_board_reply, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named for cases like replying to an existing thread (qzone_board_reply) or listing board entries (qzone_board_list). The parenthetical '(or your own)' implies a self-posting use case but gives no conditions or prerequisites.

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