Skip to main content
Glama

rename_group_file

Renames a file in a QQ group using its file ID; specify the group, current parent directory, and new name to update the listed file.

Instructions

重命名群文件 file_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>",
      "file_id": "<file_id>",
      "new_name": "<new_name>"
    },
    "name": "rename_group_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
group_idYes群号
new_nameYes
current_parent_directoryNo/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is known. The description usefully adds that the target directory must match the file's current parent, a real behavioral constraint beyond the annotations. It says nothing about permission requirements, duplicate-name handling, or failure behavior, which are relevant for a mutation.

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 compact clauses separated by a comma, with the action stated first and the constraints following. Every clause carries information; only the missing punctuation/formatting keeps it from a 5.

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?

For a four-parameter mutation with no output schema, the description covers identity sourcing and directory scoping but leaves name-validation rules and the meaning of a rename result unspecified. An agent can call it, but cannot fully predict its constraints or outcome.

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?

With only 25% schema description coverage, the description must carry weight; it explains that file_id comes from the group file list and that current_parent_directory must be the file's existing directory, covering two of the four parameters meaningfully. It adds nothing for new_name (length/character/duplicate rules) or beyond the schema's own '群号' note for group_id, so the compensation is partial.

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 opens with a specific verb+resource: '重命名群文件' (rename group file), which an agent can distinguish from siblings such as rename_group_file_folder or rename_flash_file by the resource noun alone. It does not explicitly name those alternatives, keeping it just short of a 5.

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?

It gives concrete invocation prerequisites — file_id must come from the group file list and the directory must be the file's current location — which guides correct use. However, it never states when to choose this over rename_group_file_folder or rename_flash_file, so the routing guidance is only implied.

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