Skip to main content
Glama

get_friends_with_category

Read-only

Retrieve friends grouped by category from a QQ account, optionally looking up public profiles to fill missing details.

Instructions

获取分组好友列表 Returns: 好友分组数组;buddyList 与 get_friend_list 使用相同资料字段。默认只使用列表回包,with_profile=true 主动补查,失败会报错;未返回的资料省略。

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavior: by default only the list response packet is used, with_profile triggers active supplementary lookups that raise errors on failure, and unreturned profile fields are simply omitted. These failure and omission semantics are not present in the annotations.

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 purpose is front-loaded and the whole definition is a single dense paragraph with no filler. The semicolon-chained clauses mixing purpose, return shape, and flag behavior make it slightly harder to scan, but nothing is redundant.

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?

There is no output schema, so the description carries the return-value burden, and it does: a friend-group array whose buddyList entries use the same profile fields as get_friend_list, with unreturned fields omitted. For a zero-required-parameter read tool this is close to complete; only the grouped-vs-flat distinction could be sharper.

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?

Schema coverage is 100% and the schema already explains the caching (five minutes per account) and the slow-path warning, so baseline is 3. The description earns an increment by adding semantics the schema lacks: with_profile failures surface as errors rather than partial results, and missing profile fields are dropped from the response.

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 opens with a concrete verb and resource ('获取分组好友列表', get grouped friends list) and anchors its data shape to a named sibling ('buddyList 与 get_friend_list 使用相同资料字段'), so an agent can tell it apart from get_friend_list. It stops short of explicitly saying how the grouped result differs from the flat list, so the differentiation is implied rather than stated.

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 guidance exists at the parameter level: default behavior ('默认只使用列表回包') versus opting into extra lookups with with_profile=true, including the cost ('大列表可能耗时较长' in schema) and failure mode ('失败会报错'). There is no explicit statement of when to choose this tool over get_friend_list, so tool-level selection is left to inference.

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