Skip to main content
Glama

rename_group_file_folder

Renames a file folder within a QQ group's file storage by specifying the group ID, folder ID, and new folder name.

Instructions

重命名群文件夹 将 group_id 替换为当前账号可访问的群号。

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>",
      "folder_id": "<folder_id>"
    },
    "name": "rename_group_file_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
group_idYes群号
folder_idYes
new_folder_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is partly covered. However the description adds nothing behavioral: it does not say what happens on name collision, whether the rename is reversible, whether extra scopes/permissions are needed, or which of the two name fields actually takes effect.

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

Conciseness3/5

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

Two short sentences, front-loaded with the action and followed by the parameter hint, so nothing is wasted. The brevity is under-specification rather than true conciseness, given the tool has four parameters and a mutation.

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?

This is a mutation tool with no output schema, four parameters, a 25% schema coverage and no annotations explaining reversibility or errors. The description leaves the critical question – whether to pass name or new_folder_name – entirely unresolved, which is not enough for the agent to call it correctly.

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?

Schema description coverage is only 25% – just group_id is documented as "群号". The description usefully clarifies that group_id must be a group accessible to the current account, but says nothing about folder_id or the two competing name fields (name and new_folder_name), both of which default to empty strings and are the core ambiguity for a rename operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"重命名群文件夹" states a clear verb+resource, but it is essentially a restatement of the tool name (rename_group_file_folder) with no added specificity. It does not distinguish this tool from closely named siblings such as rename_group_file or rename_flash_file, leaving the agent to infer the difference from the name alone.

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 second sentence gives a concrete usage instruction: replace group_id with a group number accessible to the current account. That is real, if minimal, guidance. There is no explicit when-not guidance and no mention of the alternative rename tools for files versus folders.

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