V.I.S.O.R.
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 |
|---|---|
| get_file_contextA | Returns a structured AST summary for a given file, including all indexed symbols (classes, functions, imports) and their line ranges. |
| store_memoryC | Persists an agent conversation turn with an embedding in the local DB. |
| get_architecture_mapC | Returns the full or partial CodeNode graph topology as a JSON string. |
| search_codebaseC | Semantic vector search across CodeNodes. Returns list of nodes. |
| get_drift_reportA | |
| get_telemetryB | Returns the current state of telemetry data. graph_nodes, context_burn, drift_alert. |
| set_hud_focusA | |
| impact_analysisB | Fetch downstream dependent files impacted by a change using BFS (max depth 5). |
| trace_routeC | Trace a path from a source node to a target node. |
| dead_code_detectionA | Finds nodes with an in-degree of 0 (no incoming callers). |
| get_symbol_contextA | |
| get_dependency_chainA | |
| build_contextB | |
| list_custom_skillsA | List all available custom V.I.S.O.R architecture skills. |
| add_custom_skillD | Adds a newly created custom skill via the UI. |
| delete_custom_skillC | Deletes a custom skill. |
| health_checkA | Basic health-check endpoint confirming the server is alive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| get_visor_skill | Fetch a specific Custom V.I.S.O.R Skill instruction pack by name. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes (e.g., build_context vs search_codebase, get_dependency_chain vs impact_analysis). Minor overlap exists between build_context and search_codebase, but descriptions clarify their different outputs (ranked context vs list of nodes).
Many tools follow a get_ prefix pattern, but there are also build_, search_, store_, set_, trace_, and compound names like dead_code_detection and health_check. This mix of verb_noun and noun_noun is inconsistent but still readable.
17 tools is slightly above the typical 3-15 range for well-scoped sets. While each tool has a clear role, the number feels a bit heavy for a code analysis server, but it's still manageable.
The tool surface covers essential code intelligence operations: search, context building, dependency analysis, drift detection, file/symbol inspection, and architecture mapping. Missing modification tools, but that's expected for a read-only analysis server.