Skip to main content
Glama

get_group_root_files

Read-only

Fetches the root-level files and folders for a specified QQ group ID and returns the group file system contents for browsing shared group files.

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the return shape (file and folder entries) and the access precondition that the group must be reachable by the current account, but says nothing about pagination, result limits, or permission failures.

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?

Very short and front-loaded: the operation comes first, then the parameter instruction, then the return note. Every fragment carries information, with no filler or repetition.

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?

For a one-parameter read tool with full schema coverage and annotations covering safety, the definition supplies what is needed: the operation, the access precondition, and the return content. No output schema exists, yet the description briefly characterizes the response, which is sufficient.

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 the single parameter already documents '群号', so the schema does the heavy lifting. The description adds only the access-scope constraint (the group must be accessible to the current account), which is a marginal gain over the schema.

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 states a specific verb and resource: retrieving the file list of a group's root directory, and clarifies the return payload (files and folders). It is clear enough to distinguish from folder-scoped retrieval, though it never names the sibling get_group_files_by_folder explicitly.

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 only guidance is 'replace group_id with a group number accessible by the current account', which is a parameter instruction rather than a when-to-use rule. It never says when to pick this over get_group_files_by_folder or get_group_file_system_info, leaving the agent to infer that 'root' means non-recursive top level.

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