Skip to main content
Glama

qzone_albums

Read-only

List QQ Zone albums with IDs, photo counts, and privacy settings; defaults to your own account, with optional QQ number to view another user's albums.

Instructions

List personal 空间相册 albums (yours by default) with ids, photo counts and privacy.

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_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinNoQQ number whose 空间 to use (default: your own)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 safety is covered. The description adds that results carry ids, photo counts and privacy and that listing defaults to the caller's own space, which is genuine added context, but it says nothing about pagination, result size limits, or visibility rules for other users' albums.

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

Conciseness5/5

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

One sentence, front-loaded with the action and resource, with the return fields and default scope packed into a short parenthetical. Nothing is wasted and nothing important is buried.

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 one-parameter read tool with full schema coverage and a rich annotation set, this is close to sufficient, and since no output schema exists, naming the returned fields is valuable. The only real gap is lack of any note on result volume or pagination for an account that may own many albums.

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%, so the single 'uin' parameter is already documented in the schema, including its default. The description's '(yours by default)' merely restates that default rather than adding format, validity, or permission details, so baseline 3 applies.

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 opens with a specific verb and resource ('List personal 空间相册 albums') and names the fields returned (ids, photo counts, privacy), which separates it from photo-level siblings like qzone_album_photos. It stops short of explicitly contrasting with qzone_create_album or qzone_delete_album, so it is clear but not fully differentiated.

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?

Usage is only implied: the agent can infer this is the discovery step before fetching photos or creating/deleting albums, but the description never states when to prefer this over qzone_album_photos or any other sibling. The '(yours by default)' note hints at scope but gives no exclusion rules 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