vs-token-safer
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_symbolA | Find a symbol DECLARATION (class/function/type/var) by name/substring — semantic index, not grep. → capped |
| find_referencesA | Every call site of a symbol (semantic, not grep) — pass |
| goto_definitionA | Jump from a 0-based position to a definition (semantic). |
| diagnosticsA | Compiler/linter errors + warnings (semantic) → capped |
| hoverC | Type/signature of the symbol at a 0-based position (hover) — a few lines, no file open. |
| document_symbolsA | Outline a file — classes/functions/types as a capped |
| read_symbolA | USE INSTEAD OF Read on a file when you only need ONE function/class — returns just that named declaration's source (its span), not the whole file (the read twin of replace_symbol_body). |
| renameA | Rename the symbol at a 0-based position project-wide (semantic — every reference, not a sed). PREVIEW by default (affected |
| replace_symbol_bodyA | Change a whole function/class/method by NAMING it — USE INSTEAD OF Read-the-file + Edit (the outline gives the span, so you skip the whole-file Read and exact-match line-counting). PREVIEW by default; apply=true writes in ONE call. |
| insert_symbolA | Insert text next to a named declaration — position=after (default)|before. The outline gives the point (no Read). PREVIEW by default; apply=true writes. Use instead of Read-then-Edit to add a declaration. |
| safe_deleteA | Delete a named declaration — USE INSTEAD OF Edit-deleting it; REFUSES while still referenced (lists the refs, force=true overrides) so a delete can't silently orphan call sites. PREVIEW by default; apply=true writes. |
| find_filesA | Find files by name (substring or glob like *Manager.cpp) — replaces Bash |
| search_textA | Raw text/regex search (string literals, comments, config — what the symbol index can't answer). Replaces Bash grep when you need text, not symbols. → capped |
| concept_searchA | FUZZY search for a concept you can't name ("how does auth work"). Mines a dictionary from the repo's own identifier+comment co-occurrence (no embeddings, nothing sent) → ranked |
| detect_changesA | Review a diff by IMPACT: git diff → changed symbols → blast radius (callers) + LOW/MED/HIGH risk. → capped |
| vts_adminA | vs-token-safer admin/meta ops (rarely needed reflexively) — set |
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 16 tools
Every tool targets a clearly distinct action/resource: semantic symbol search, references, goto definition, file search, diagnostics, hover, outlines, targeted reads, rename/replace/insert/delete, text search, fuzzy concept search, diff review, and admin. Overlapping pairs are explicitly cross-referenced in descriptions to steer agents correctly.
Most tools follow a verb_noun pattern (search_symbol, find_references, replace_symbol_body, detect_changes) and all names are lowercase snake_case. Minor deviations such as diagnostics, hover, rename, safe_delete, concept_search, and vts_admin break the pattern, but the intent is still clear.
At 16 tools this is one above the typical 3-15 sweet spot, but the count is justified by the broad semantic-code domain: search, navigation, diagnostics, refactoring, review, and admin. No tools feel redundant or purely decorative.
The set covers the full lifecycle for its stated purpose: locate (semantic/text/concept/file), understand (hover, outline, read, diagnostics), modify safely (rename, replace_body, insert, safe_delete with reference checks), and review impact (detect_changes, find_references). It also includes admin/indexing operations, leaving no obvious dead ends for code intelligence workflows.