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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_create_folder

Create a folder or empty virtual file in the RAGFlow file manager, automatically adding a numbered suffix if the name is already taken.

Instructions

Create a folder (or an empty virtual file) in the file manager; a taken name gets a numbered suffix.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName; must not contain '/'
typeNofolder, or virtual for an empty placeholder filefolder
parent_idNoFolder ID; omit for the root folder of the file manager

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, closed-world behavior, so safety is covered. The description adds one genuinely useful behavioral fact — a taken name receives a numbered suffix rather than overwriting or failing — but says nothing about permission requirements, parent/root resolution, or nesting limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the primary action and the most surprising behavior (name-collision suffixing) front-loaded. Nothing is wasted and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and 100% parameter coverage, the description's main remaining obligation is behavioral context, and it delivers the key collision-renaming detail. Gaps are minor: no mention of permissions or what parent_id=null means, though the schema covers the latter.

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 description coverage is 100%, including the '/' restriction on name, the folder/virtual enum, and parent_id defaults, so the schema carries the parameter burden. The description's mention of 'empty virtual file' loosely reinforces the type parameter but adds no format or edge-case detail beyond the schema.

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 names a specific verb and resource ('Create a folder ... in the file manager') and clarifies the dual mode of producing an empty virtual file. It is unambiguous against siblings like ragflow_upload_file or ragflow_list_files, though it does not explicitly reference an alternative.

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 create a folder versus a virtual file placeholder, nor when to prefer this over upload_file or move_files. The 'type' semantics are implied but never framed as a decision the agent must make.

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