fsq-codebase
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERBOSE | No | Enable verbose output (corresponds to --verbose flag) | false |
| INDEX_PATH | Yes | Path to the codebase index file (corresponds to --index argument) |
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 |
|---|---|
| codeinfuseA | INTERACTIVE code context search. First call (selection=0): Returns numbered list of matches. CRITICAL: After first call, you MUST IMMEDIATELY call AskUserQuestion to let user pick a number - DO NOT skip this step or pick for them. Second call (selection=N): Returns full context for selection N. User selections are logged for training data. |
| search_codeA | Search codebase for relevant functions/classes. Returns top matches with IDs. ALWAYS use this first to find candidates, then use AskUserQuestion to let user pick. After user selects, use extract_code_context with the entity_id. |
| extract_code_contextA | Get code context for a specific entity (from search_code results). Returns signatures of function/class with callers and callees. Use entity_id from search_code results for precise targeting. |
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 3 tools
codeinfuse and search_code both return search results and involve user selection, creating overlap and ambiguity about which to use. extract_code_context is distinct but depends on search_code.
The tool names are inconsistent: codeinfuse is a single word (camelCase?) while extract_code_context and search_code use snake_case and follow a verb_noun pattern. This inconsistency reduces clarity.
3 tools is a reasonable minimal set for a codebase search and context retrieval server. Each tool serves a distinct step in the workflow, so the count feels appropriate.
The tools cover search, user selection, and context extraction, but missing a direct context retrieval by known ID without prior search. This is a minor gap.