Skip to main content
Glama

qzone_visitors

Read-only

Retrieve recent QQ Zone visitor records with visit time and source for your own space by default or another user's space when permission is granted.

Instructions

QQ空间 访客记录: who visited a 空间 recently (yours by default; others need permission), with time and source.

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

Input Schema

NameRequiredDescriptionDefault
uinNoQQ number whose 空间 to use (default: your own)
pageNoPage (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the description is not burdened with safety disclosure. It still adds real behavioral context: the default target is the caller's own 空间, querying another user's requires permission, and records carry time and source metadata. It does not discuss pagination limits or how much history is returned, which keeps it below a 5.

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 that leads with the resource (访客记录) and packs scope, permission caveat, and returned fields into one line with no filler. The parenthetical compresses two distinct ideas, making it dense but still parseable.

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 two-parameter read tool with no output schema, the description covers the essentials: what is fetched, whose data, and the shape of each entry (time plus source). Pagination behavior is left entirely to the schema, which is a minor gap given page is optional.

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 both parameters (uin and page) are already documented in the schema, including uin's 'default: your own' semantics. The description's 'yours by default; others need permission' largely restates the uin default while adding only the permission caveat, so the 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 names a specific resource — recent 空间 visitor records — and specifies what each record contains (time and source), which is far more concrete than the bare tool name. It does not explicitly distinguish itself from the nearest siblings such as qzone_friends or qzone_intimacy, 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 Guidelines3/5

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

Usage context is implied rather than spelled out: 'yours by default; others need permission' tells the agent the default scope and that querying someone else requires authorization, which is useful. However, there is no explicit when-to-use vs. when-not guidance and no sibling is named as an alternative for related social-graph queries.

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