CodeSeeker-MCP
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 |
|---|---|
| check_ugrep_installationB | Check if ugrep is installed and get installation instructions |
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 possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
The single tool follows a consistent verb_noun pattern (check_ugrep_installation), and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.
A single tool is too few for a server named 'CodeSeeker-MCP', which suggests a broader purpose related to code searching or analysis. This minimal toolset feels thin and under-scoped for the implied domain.
The toolset is severely incomplete for the apparent domain of code seeking. It only checks for ugrep installation, lacking any tools for actual code searching, analysis, or other related operations, creating significant gaps that will cause agent failures.