Skip to main content
Glama

trans_group_file

Transfers a group file and replaces its file_id in the group file list; requires matching file operation permissions.

Instructions

转存群文件 替换群文件列表中的实际 file_id;需要对应文件操作权限。 Returns: { ok: true }

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

Input Schema

NameRequiredDescriptionDefault
file_idYes
group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 bar is lower; the description still adds real value by stating a permission requirement ("需要对应文件操作权限") and the return shape ("Returns: { ok: true }"). However it never explains what the operation actually does to the group's file list, so the mutation's effect stays opaque.

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?

Very short and front-loaded, with the return value last, which is good structure. But the second clause is compressed to the point of ambiguity, so brevity costs comprehension rather than earning its place.

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?

A two-parameter mutation tool with partial annotations and no output schema: the definition supplies the permission caveat and the return value, which covers the main gaps. It remains incomplete on what the mutation does to the group file list and on parameter meaning, which for a write operation is a notable omission.

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 0% and both parameters (group_id, file_id) are undocumented in the schema, so the description must carry the load. It only alludes to file_id indirectly ("替换群文件列表中的实际 file_id") and says nothing about group_id or accepted id formats, leaving the meaning of both parameters largely unexplained.

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?

The verb+resource ("转存群文件" / save group file) is stated, but the qualifier "替换群文件列表中的实际 file_id" is cryptic — it does not make clear whether the file is copied into the group, replaced in place, or merely referenced. An agent can guess the general area but cannot confidently distinguish this from upload_group_file or move_group_file based on the text.

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 when-to-use or when-not-to-use guidance and no named alternative, despite a crowded sibling set of group-file tools (upload, move, rename, delete). The only condition given is the permission requirement, which is a prerequisite rather than a selection rule.

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