Skip to main content
Glama

get_friend_list

Read-only

Retrieve your QQ friend list, including account IDs, nicknames, remarks, and available public profiles. Optionally fetch missing profile details on demand, cached per account.

Instructions

获取好友列表 Returns: 好友列表,包含账号、昵称、备注及回包已有的公开资料;with_profile=true 时主动补查,失败会报错。未返回的资料省略,零、空字符串和 false 保留。

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

Input Schema

NameRequiredDescriptionDefault
with_profileNo主动补查好友公开资料,按账号缓存五分钟;大列表可能耗时较长

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and non-destructive behavior. The description adds meaningful return semantics: which fields appear, that omitted fields stay omitted, that zero/empty string/false are preserved, and that a failed with_profile supplement raises an error.

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?

The description is compact and front-loaded, covering purpose, return payload, and caveats in two sentences. The embedded "Returns:" label and dense semicolon clauses are slightly awkward but not wasteful.

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?

With one optional parameter and no output schema, the description appropriately explains the return fields and omission semantics. It is nearly complete, though it omits ordering, pagination, or large-list performance context that would help for a list-returning tool.

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 coverage is 100% and already describes with_profile as an active supplement with five-minute caching and possible slowness on large lists. The description adds only the failure-error behavior, so a baseline 3 is appropriate.

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?

States a specific verb and resource ("获取好友列表") and lists the returned fields. It is clear what the tool does, but it does not distinguish itself from siblings such as get_unidirectional_friend_list or list_contacts.

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 description gives no explicit guidance on when to use this tool versus alternatives, and it does not name any sibling. It explains only the with_profile parameter behavior, which is usage detail rather than tool-selection guidance.

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