Skip to main content
Glama

get_group_files_by_folder

Read-only

Retrieve files and folders from a specified QQ group folder to browse shared group resources using a group ID and optional folder identifiers.

Instructions

获取群子目录文件列表 将 group_id 替换为当前账号可访问的群号。 Returns: 群文件系统信息(文件与文件夹列表)。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>"
    },
    "name": "get_group_files_by_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNo
group_idYes群号
folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds the accessible-group prerequisite and summarizes the returned file and folder lists, but does not discuss errors, pagination, or behavior when folder selectors are left at their defaults.

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

Conciseness5/5

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

The description is compact and front-loads the subdirectory-listing purpose, followed by the group_id prerequisite and return summary. Each clause contributes useful information and there is no filler.

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?

The return summary partially compensates for the missing output schema, and the annotations cover the safety profile. However, the definition is not complete enough for reliable folder-targeted invocation because the two folder selectors and their interaction remain undocumented, leaving the central “by folder” behavior ambiguous.

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?

Only group_id gains meaning beyond the schema: the current account must have access to that group. With schema coverage at 33%, leaving folder and folder_id unexplained—including path versus ID semantics, whether they are alternatives, and what their empty defaults do—is a material gap.

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 the operation, resource, and subdirectory scope, while the return clause clarifies that both files and folders are listed. It does not explicitly differentiate the tool from the root-file or file-system-info siblings, so it is clear but not fully distinctive.

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?

The explicit invocation guidance is limited to replacing group_id with a group number accessible to the current account. Subdirectory scope implies when the tool is useful, but there is no when-not guidance, named alternative, or explanation of which folder selector to supply.

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