Skip to main content
Glama

qzone_friends

Read-only

Retrieve your QQ Zone friends list, including 空间 groups and 亲密度 scores, to see how QQ Zone organizes and ranks your contacts.

Instructions

Friends as QQ空间 sees them, with 空间 grouping and 亲密度 (intimacy score).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results come from the QZone viewpoint and include grouping and intimacy fields, which is meaningful since no output schema exists, but it says nothing about whether the list is complete, ordered, or paginated.

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 short sentence with no padding, and the distinguishing details (grouping, intimacy) are front-loaded. The phrasing 'as QQ空间 sees them' is slightly evocative rather than precise, which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only tool with annotations covering safety and no output schema to lean on, the description supplies the essential return shape (friends plus 空间 grouping and 亲密度). Nothing an agent needs in order to call it successfully is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the sentence does not misrepresent any inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (friends list) and the QZone-specific perspective, plus the two data facets returned: 空间 grouping and 亲密度. However it uses a noun phrase with no verb, so an agent must infer that this is a read/list operation, and it never distinguishes itself from the close sibling get_friends_with_category.

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 guidance, no exclusion, and no named alternative. With a sibling like get_friends_with_category in the catalog, an agent has no textual basis for choosing between them beyond guessing from the names.

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