Skip to main content
Glama

delete_group_file

Destructive

Deletes a specified QQ group file by group ID and file ID. Requires file operation permissions.

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

Input Schema

NameRequiredDescriptionDefault
file_idYes
group_idYes群号

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?

注解已经声明 destructiveHint=true、readOnlyHint=false 和 openWorldHint=true,因此破坏性风险已由结构化字段传达。描述在此基础上补充了两条有实际价值的信息:权限要求,以及 file_id 必须取自群文件列表的真实值。但删除是否不可逆、删除后关联记录会怎样、返回什么,都没有说明,因此只是适度加分。

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?

只有一句话,删除对象前置,权限要求后置,没有冗余修饰。但内容用分号拼接,读起来稍显密集,且缺少明确的结构化分隔。

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?

对于一个只有两个参数、没有输出 schema、且注解已覆盖安全属性的删除工具,当前描述已交代操作对象、id 来源和权限前提。不过,“对应文件操作权限”具体指哪一级权限并未说明,失败情形和删除范围(是否影响群文件计数/他人可见性)也留有空白,因此整体完整度只能算中等。

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 描述覆盖率只有 50%,file_id 在 schema 中完全没有说明,而描述正是针对这一点给出了关键补充:必须使用群文件列表中的实际 file_id。group_id 仅有“群号”说明,描述没有进一步补充它的格式或取值范围。整体属于部分补偿,未完全覆盖参数含义。

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?

明确写出了具体动作和资源(“删除群文件”),并用“替换群文件列表中的实际 file_id”把该操作与同级工具中的 delete_group_file_folder、delete_flash_file 区分开来。它没有明确点名任何同级工具作为替代项,但删除对象已经无歧义。

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?

说明了前置条件(“需要对应文件操作权限”),但未说明何时该用这个工具、何时该改用文件夹删除或 flash 文件删除,也没有说明删除失败或文件已被删除时的处理方式。对群文件删除这一具体操作而言,使用语境是隐含的,并未明示。

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