Skip to main content
Glama

qzone_board_list

Read-only

Read QQ Zone message board posts and their replies for your own account or a specified QQ number, with pagination to fetch entries by count and offset.

Instructions

Read a 空间 留言板 (message board) — yours by default — with replies.

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": "qzone_board_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
numNoHow many (max 20)
uinNoQQ number whose 空间 to use (default: your own)
startNoOffset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds that replies are returned alongside the board and that the target defaults to the caller's own space, which is genuinely useful beyond the annotations, but it says nothing about ordering, pagination limits beyond the schema, or visibility/permission constraints.

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 the resource and the default scope stated immediately; nothing is padded. It is arguably too terse for the remaining gaps, but there is no wasted wording.

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 read-only list tool with fully documented parameters, no output schema, and clear annotations, the definition covers the essentials and even flags that replies are included. It stops short of distinguishing this board reader from other Qzone read tools, which is the main thing an agent still has to guess.

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 num ('max 20'), uin ('default: your own') and start ('Offset') all documented, so the baseline is 3. The description's 'yours by default' merely restates the uin default already in the schema and adds no new syntax or semantics.

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 uses a specific verb ('Read') with a specific resource ('空间 留言板 (message board)') and notes the default scope ('yours by default') plus that replies are included. That is enough to know what the tool returns, though it never contrasts with lookalike siblings such as get_qzone_msg_list or the write-side qzone_board_* tools.

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 / when-not-to-use guidance and no named alternative. The only contextual hint is 'yours by default', which describes a default value rather than a selection rule. An agent must infer from the name that this is the read counterpart to qzone_board_post/reply/delete.

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