symbiont
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 |
|---|---|
| get_file_outlineA | Returns high-level symbol declarations (functions, classes, interfaces, types, enums, variables) with line ranges and signatures without dumping raw file bodies. |
| find_all_usagesA | Performs deterministic AST traversal to return every exact reference, import, definition, and call-site across the codebase. |
| rename_symbolA | Applies syntactically safe, AST-level renames across all consumers and returns unified diffs. |
| check_architecture_rulesA | Evaluates the dependency graph against declarative architectural rules (.symbiontrc.yaml) and returns actionable boundary violations. |
| get_dependency_graphA | Builds a module dependency graph, tracking direct imports, dependents, and circular dependency cycles. |
| set_workspace_rootA | Sets or re-indexes the active project workspace root directory. |
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 6 tools
Each tool addresses a clearly distinct concern: per-file symbol outlines, module dependency graphs, exact usages, refactoring, architecture rule validation, and workspace management. Related tools like get_dependency_graph and check_architecture_rules are separated by build vs. evaluate, preventing confusion.
All tool names follow a consistent snake_case verb_object pattern (get_file_outline, rename_symbol, set_workspace_root, etc.). There are no vague verbs or mixed casing conventions.
Six tools is well-scoped for a code intelligence and refactoring server. Each tool earns its place and covers a distinct phase without redundancy.
The set covers the core lifecycle: workspace setup, navigation, dependency analysis, usage discovery, renaming, and architecture validation. Minor conveniences like a get_workspace_root or deeper symbol-detail lookup are absent, but they are not required for the main workflows.