Skip to main content
Glama

get_group_list

Read-only

Retrieves the QQ groups associated with the account, returning group information for use in group management and messaging workflows.

Instructions

获取群列表 Returns: 群信息对象数组。

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

Input Schema

NameRequiredDescriptionDefault
no_cacheNo

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only a vague return statement ('群信息对象数组') and says nothing about the caching behavior implied by the no_cache parameter, pagination, or freshness of results.

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?

Two short clauses, front-loaded with the action, with no filler. The 'Returns:' clause is marginally useful given there is no output schema, though it conveys almost nothing concrete.

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?

For a no-argument, no-output-schema tool this could have been adequate, but the sole parameter is undocumented in both schema and description, and the scope of the returned list is undefined. An agent cannot tell what it will actually receive or how to control caching.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter (no_cache) with 0% schema description coverage, and the description never mentions it. No meaning is added about what bypassing the cache does, its default effect, or when it should be set.

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 a specific verb+resource ('获取群列表' / get group list), which is unambiguous on its own. It does not, however, distinguish this from nearby siblings such as get_group_info, get_group_detail_info, or get_friend_list, so an agent must infer the boundary itself.

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?

There is no guidance on when to use this versus get_group_info or get_group_detail_info, and no stated prerequisites or exclusions. The agent is left to guess whether this returns all groups, joined groups, or a cached snapshot.

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