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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_list_files

Read-only

List files and folders in a specified folder or root, with options for sorting, paging, and keyword filtering, to browse and manage RAGFlow knowledge base content.

Instructions

List files and folders in a file-manager folder (root when parent_id is omitted), plus the folder above it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ragflow_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo
pageNoPage number, starting at 1
orderbyNoSort field, e.g. create_time or namecreate_time
keywordsNoMatch file names
page_sizeNoItems per page (RAGFlow caps it at 100)
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

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description adds one useful behavioral detail, that response also includes the folder above the listed folder, but says nothing about pagination behavior or ordering defaults.

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?

A single front-loaded sentence with no filler. The trailing phrase 'plus the folder above it' is slightly ambiguous but does convey real information.

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 an output schema present, return format need not be described, and the description covers the core listing scope plus root default. Minor gaps around pagination and sorting fall back on the well-documented schema.

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 high (83%), so the schema documents most parameters, including parent_id's root behavior and page/page_size limits. The description's only added semantic is the parent-folder return context, which is minor duplication of 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?

States a concrete verb and resource (list files and folders in a file-manager folder) and clarifies the root behavior when parent_id is omitted. It does not explicitly distinguish itself from near-siblings like ragflow_list_documents or ragflow_get_parent_folder, keeping it just below a 5.

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?

The clause 'root when parent_id is omitted' implies when the tool applies, but there is no explicit when-to-use guidance or named alternative (e.g. get_parent_folder, list_documents). Usage must be inferred from the parenthetical.

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