Skip to main content
Glama
ragflow-kb-mcp
by feci

ragflow_list_datasets

Read-only

Lists RAGFlow knowledge base datasets with IDs, descriptions, document and chunk counts, and supports filtering, ordering, and pagination.

Instructions

List datasets (knowledge bases) with IDs, descriptions and document/chunk counts.

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_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo
nameNoExact dataset name filter
pageNoPage number, starting at 1
orderbyNocreate_time
keywordsNoMatch dataset names
page_sizeNoItems per page
parser_idNoOnly datasets with this chunking method
dataset_idNoReturn only this dataset

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 declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only a hint of what a result row contains, and says nothing about pagination, default sort order, or how filters combine – context the annotations don't provide.

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 front-loaded sentence with zero filler; the resource and the payoff (IDs, descriptions, counts) come first.

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?

An output schema exists, so return values needn't be explained, and annotations cover safety. But for an 8-parameter listing tool the description omits that filtering, sorting and pagination are even available, leaving the agent to discover those capabilities entirely from the 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?

The description mentions no parameters at all, not even that name/keywords/dataset_id filters or page/page_size paging exist. Schema coverage is 75%, so most parameters are self-documented, but 'desc' and 'orderby' have no explanation anywhere – an agent must guess that 'desc' means descending order.

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 and resource ('List datasets'), disambiguates the term with '(knowledge bases)', and names the key returned fields. It's clearly distinct from ragflow_get_dataset/ragflow_create_dataset/ragflow_delete_datasets by virtue of being a multi-item listing, though it never names those siblings explicitly.

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?

Usage is only implied: an agent can infer you call this to discover datasets before operating on one, but the description never says when to use it versus ragflow_get_dataset (single-dataset lookup) or ragflow_list_documents, and gives no prerequisites or exclusions.

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