Skip to main content
Glama

move_group_file

Move a file from one directory to another in a QQ group's file list by specifying the group, file identifier, current directory, and target directory.

Instructions

移动群文件 目录和文件标识均来自该群文件列表。

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>",
      "parent_directory": "<parent_directory>",
      "target_directory": "<target_directory>"
    },
    "name": "move_group_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
group_idYes群号
parent_directoryYes
target_directoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 mutation profile is covered. The description adds the useful constraint that both directory and file identifiers must originate from the group's file list, but does not say what happens if the target directory is missing or already contains a same-named file.

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, action first, constraint second, with no filler. It is appropriately sized, though its brevity is also part of why key semantics are missing.

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?

A four-required-parameter mutation tool with 25% schema coverage and no output schema needs more than this. The undefined role of parent_directory versus target_directory, plus silent failure/conflict behavior, leaves an agent under-informed before a write operation.

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% — only group_id (群号) is documented. The description does not explain the critical distinction between parent_directory and target_directory, which is the main ambiguity an agent must resolve to call this tool correctly.

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 clear verb+resource pair: "移动群文件" (move group file). An agent can tell it is a move operation on group files, but nothing distinguishes it from siblings such as rename_group_file or trans_group_file, which are plausible confusions.

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 statement of when to use this tool versus rename/trans/upload alternatives, and no preconditions or exclusions. The only contextual hint is that identifiers come from the group's file list, which is provenance rather than usage guidance.

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