cindex
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_codeA | Semantic search over this repo's code and docs. Finds code by meaning (e.g. "where do we refuse a mismatched database"), not just exact text — use it before falling back to grep. Returns JSON: file_path, start/end lines, symbol, score, snippet. Optional path_prefix restricts results to a subtree (e.g. "src/"). |
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 between tools. The tool is clearly and uniquely defined.
The single tool name 'search_code' follows a clear verb_noun pattern (snake_case), which is consistent within the server.
One tool is on the lower end of appropriateness. While the server's purpose (semantic code search) is narrow, a single tool may feel thin for a typical MCP server; however, it is not extreme.
The single tool covers semantic search over code and docs, which appears to be the server's complete purpose. Minor gaps like index management are absent, but not necessarily required based on the description.