Skip to main content
Glama
Sign In
ragflow-kb-mcp

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_delete_files

Destructive

Permanently delete specified files or folders, including their contents, from the file manager by providing file IDs.

Instructions

Permanently delete files or folders (with their contents) from the file manager.

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": {
      "file_ids": "<file_ids>"
    },
    "name": "ragflow_delete_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idsYesFiles or folders to delete

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description does add value beyond that by saying 'Permanently' and 'with their contents', warning that deleting a folder cascades to its children. It stops short of stating consequences for linked datasets/documents or whether any recovery path exists.

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?

One sentence, front-loaded with the destructive verb and the resource, with no filler. It could be marginally tighter, but every word carries information relevant to invoking the tool correctly.

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?

With one required parameter, rich annotations, and an output schema, the description covers the minimum needed to call it. However, for an irreversible destructive operation it omits whether linked datasets or documents are affected and what happens to partially invalid IDs, leaving real gaps.

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 coverage is 100% and the single parameter file_ids is documented as 'Files or folders to delete', which the description largely repeats. The only nuance the description contributes is confirming folder IDs are valid inputs, which the schema already implies; no id format, batching limits, or partial-failure behavior is described.

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?

States a specific verb (delete) and resource (files or folders) plus the cascading scope ('with their contents'). It is unambiguous what the tool does, but it never names the adjacent alternatives it could be confused with, notably ragflow_delete_documents or ragflow_move_files, so sibling differentiation is left to the agent.

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 guidance on when to choose this over ragflow_delete_documents (documents vs. file-manager files) or ragflow_move_files as a non-destructive alternative. The only implied usage is the word 'delete' itself; no prerequisites, exclusions, or conditions are given.

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