MCP keyword search
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_fileA | Search for a keyword within a file and return all matching lines with line numbers |
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 1 tool
With only one tool, there is no ambiguity or risk of confusing it with others. The tool's purpose is clearly defined as searching for a keyword within a file.
The tool name follows a clear verb_noun pattern: search_file. This is consistent and predictable, even with only a single tool.
A single tool is extremely minimal, but for a server specifically focused on keyword search in files, it might be acceptable. However, it feels thin and could benefit from additional related tools like directory search or multi-file search.
The server only supports searching within a single file, lacking capabilities such as directory-wide search, regex support, or multi-file search. These are significant gaps for a keyword search tool, rendering the surface severely incomplete.