Baloosearch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_filesC | Search for terms in files using KDE baloosearch. Query Syntax Examples:
|
| show_file_wordsA | Show indexed content & meta-data in a file using KDE balooshow. This tool retrieves all the indexed words & meta-data from a specific file that has been indexed by KDE's Baloo search system. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: search_files searches across files for terms, while show_file_words displays indexed content and metadata for a specific file. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern with snake_case: search_files and show_file_words. The naming is predictable and readable throughout.
With only 2 tools, the server feels thin for its apparent scope of file search and metadata display. A typical search system might include additional operations like listing indexed files, updating indexes, or filtering results, making this set under-scoped.
Inferring the domain as file search and indexing, there are significant gaps: no tools for managing the index (e.g., refresh, status), listing available files or properties, or performing advanced queries beyond basic search. This limits agent workflows and could lead to dead ends.