Skip to main content
Glama

get_unidirectional_friend_list

Read-only

Retrieves the QQ account's unidirectional friend list, helping identify contacts with a one-way friendship relationship rather than a mutual connection.

Instructions

获取单向好友列表

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": "get_unidirectional_friend_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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 nothing beyond that: no note on whether the list is paginated, how large it typically is, or whether it reflects the caller's account only, which matters given openWorldHint=true.

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

Conciseness3/5

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

It is a single front-loaded phrase with no waste, which is structurally fine, but the brevity crosses into under-specification rather than efficiency. One short clarifying clause about what "单向" means would have cost little and removed the main ambiguity.

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

Completeness2/5

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

With no parameters, no output schema and a terse description, the agent has no information about what the returned entries contain (user IDs, nicknames, timestamps?) or how to interpret a one-way relation. For a read-only list tool this is a real gap, since the return shape must be inferred entirely.

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; the baseline for a no-parameter tool is 4. The description neither helps nor hurts here.

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?

"获取单向好友列表" names a verb (get) and a resource (unidirectional friend list), so the basic action is identifiable. However, "单向好友" (one-way friend) is unexplained jargon: an agent cannot tell whether this means followers-only, people who added you without reciprocation, or a platform-specific relation type, so it does not cleanly separate from the sibling get_friend_list.

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?

The definition offers no when-to-use guidance at all. It never says how this differs from get_friend_list or list_friend_requests, nor whether it requires the user to be logged in or to have any special relationship state.

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