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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_list_search_apps

Read-only

List saved search apps in RAGFlow to review configurations that answer questions from datasets, with pagination, keyword filtering, and sorting.

Instructions

List search apps (saved search configurations that answer questions from datasets).

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

Input Schema

NameRequiredDescriptionDefault
descNo
pageNoPage number, starting at 1
orderbyNocreate_time
keywordsNoMatch search app names
page_sizeNoItems per page

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3/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 covered and the bar is lower. The description adds the only real value here: a definition of what a search app is. It says nothing about pagination defaults, total counts, or ordering behavior.

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 core verb and resource lead. It is arguably too terse for a five-parameter listing tool, but nothing is wasted.

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 need not be explained, and this is a simple read-only list tool. Still, the description omits pagination/ordering behavior and the meaning of two parameters, leaving gaps an agent would hit on first call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 60%: page, page_size, and keywords are documented in the schema, but 'desc' and 'orderby' have no description anywhere. The tool description adds zero parameter meaning, so it does not compensate for the undocumented fields.

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 ('List') and resource ('search apps'), and the parenthetical defines what a search app is so an agent unfamiliar with the domain understands it is a saved search configuration. It does not explicitly contrast with siblings like ragflow_get_search_app or ragflow_list_datasets, keeping it 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no mention of when to prefer ragflow_get_search_app or a keyword search, and no note about iterating pages versus listing all. The usage is only implied by the verb 'List'.

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