symbols
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 |
|---|---|
| syms_listB | Extract top-level symbols (functions, classes, types, constants) from source files |
| syms_importsB | Parse import statements from source files |
| syms_depsB | List files that a given file depends on (imports from) |
| syms_dependentsC | List files that depend on (import from) a given file |
| syms_impactC | Impact analysis: direct and transitive dependents of a file |
| syms_searchA | Search for symbols by name across a project. Matches are ranked: exact > prefix > contains (case-insensitive). |
| syms_graphA | Project-wide dependency graph summary with hot spots, heaviest importers, and circular dependencies |
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 7 tools
Most tools have distinct purposes, but there is some overlap: syms_dependents and syms_impact both deal with dependents (though impact includes transitive), and syms_deps and syms_imports both relate to dependencies vs. import statements. This could cause minor confusion.
All tools follow a consistent pattern: 'syms_' prefix plus a descriptive second part using underscores. No mixed conventions (all lowercase snake_case).
Seven tools is well-scoped for a code symbol and dependency analysis server. Each tool covers a focused aspect without being overwhelming or too sparse.
The set covers dependency analysis, symbol listing, and search. Minor gaps exist, such as no tool for detailed symbol metadata or reference finding, but the core analysis workflow is well-supported.