Skip to main content
Glama

list_tools_by_category

Read-only

Lists every tool grouped by category with an optional category filter, helping you find the right QQ account operation for your task.

Instructions

Overview of every tool grouped by category (message, friend, group_info, group_admin, group_file, group_album, qzone, qzone_web, chat, events, extended…), to find the right one.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly this category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: it explains the grouping structure and enumerates the actual category buckets (message, friend, group_info, group_admin, group_file, group_album, qzone, qzone_web, chat, events, extended), which tells the agent how results are organized.

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 sentence, front-loaded with the core purpose before the category enumeration, with no filler. The long parenthetical is dense but each item carries information the agent cannot get from the schema.

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?

There is no output schema, so the description should ideally state what the grouped listing contains (tool names only, or names plus descriptions/purposes). It conveys the grouping and categories adequately for a one-parameter discovery tool, but leaves the shape of the result implicit.

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%, so the single `category` parameter is already documented as "Only this category," establishing baseline 3. The description's parenthetical list supplies candidate category values the schema does not enumerate, but it is explicitly open-ended ("…") and never states matching behavior (exact vs. prefix, case sensitivity).

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 names the resource (every tool), the organizing dimension (category), and an intent ("to find the right one"), which clearly separates it from the sibling tools that fetch concrete data like get_friend_list or list_filesets. The noun-heavy phrasing ("Overview of...") is weaker than an explicit verb such as "list", but the purpose is still unambiguous.

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?

"To find the right one" implies the discovery use case: call this when you don't yet know which tool to use. However, there is no explicit when-not guidance (e.g., don't call this if you already know the tool name) and no named alternative or follow-up pattern for acting on the returned list.

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