Skip to main content
Glama

qzone_intimacy

Read-only

Rank QQ Zone friends by intimacy score to identify whom you care about or who cares about you. Choose mine or theirs to switch between your ranking and their ranking.

Instructions

空间 friendship ranking: who you care about most (mine) or who cares about you most (theirs), by 亲密度.

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

Input Schema

NameRequiredDescriptionDefault
directionNomine = 我在意谁, theirs = 谁在意我mine

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly=true, destructive=false, and openWorld=true, so the bar for safety disclosure is low. The description adds the ordering trait (results are ranked by 亲密度), which is useful and is not in the annotations, but it says nothing about result size, pagination, or whether empty results are possible.

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?

It is a single front-loaded sentence that defines the ranking and then maps each mode to its meaning. It is compact and wastes nothing, though the mixed-language phrasing (空间, 亲密度) slightly reduces immediate readability.

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?

This is a simple one-parameter read tool with no output schema, so the description carries the burden of explaining the return value. It implies a ranked list of people by intimacy but never confirms the shape, such as a scored list versus a single top match.

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%, and the single enum's semantics are already documented in the schema itself, so the description mostly restates that same direction mapping. It still reinforces the default value and how to read the rankings, but it adds little beyond what structured fields already define.

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?

Names a concrete resource, a friendship intimacy ranking, and splits it by direction. An agent can tell this apart from list-style siblings such as qzone_friends or qzone_like_list, although no explicit verb like "get" or "list" is used.

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?

The description clarifies the two modes (who you care about versus who cares about you), which helps with the direction choice. However, it gives no guidance on when to pick this over sibling friend or like-list tools, and it states no prerequisites, such as login or permission requirements.

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