context-sniper-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_repoA | Scan a repository and build a lightweight chunk index at /.context-index/chunks.json. Run this once before search_code (and re-run after significant code changes). |
| search_codeA | Search the previously built chunk index with a BM25-style keyword score and return a compact evidence packet (FILE / LINES / SCORE + snippet) instead of full files. Call index_repo first if no index exists. |
| read_snippetA | Read an explicit line range from a single file inside root. Use this only after search_code narrows down a location and the returned snippet isn't enough context. Capped at 300 lines per call. |
| run_test_filteredA | Run one of a fixed allowlist of test commands (no arbitrary shell) and return only the filtered failure-relevant output: command, exit code, and lines matching error/failed/assert/expected/traceback/test-file-path, tail-capped at 120 lines (falls back to last 80 raw lines if nothing matches). |
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 4 tools
Each tool has a distinct, non-overlapping purpose: indexing, searching, reading snippets, and running tests. No ambiguity in choosing between them.
All tool names follow a consistent verb_noun (or verb_noun_adjective) pattern in snake_case, making the action and target immediately clear.
Four tools cover the core workflow (index, search, read, test) without extraneous clutter. The count fits the domain perfectly.
The tool set provides a complete loop for code understanding and test failure analysis: build index, search, read context, run tests with filtered output. No obvious gaps for the stated purpose.