qzone-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qzone_check_loginA | 检查 Edge 登录状态。确认 Edge 已用 --remote-debugging-port=9222 启动且已登录 QQ 空间。 |
| qzone_get_feed_listA | 获取指定 QQ 号的说说列表,返回 tid、内容、时间等。评论前需先用本工具拿到 tid。 |
| qzone_comment_feedA | 对指定说说发表评论。需先通过 qzone_get_feed_list 拿到 tid。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: login check, feed listing, and commenting. The descriptions explicitly state the workflow dependency (get tid before commenting), eliminating ambiguity. No two tools could be reasonably confused.
All three tools use the same qzone_ prefix and snake_case verb_noun pattern: qzone_check_login, qzone_get_feed_list, qzone_comment_feed. The verbs are distinct but consistent with their actions.
Three tools is on the low end but still within a reasonable focused scope for a narrow Qzone commenting workflow. The set avoids bloat, though it could benefit from one or two additional operations.
The login -> list feeds -> comment workflow is complete, but the surface lacks common Qzone operations such as publishing a post, liking, deleting a comment, or reading existing comments. These are notable gaps for a server named qzone-mcp.