GDScript Code Analyzer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUST_LOG | No | Set logging level (e.g., debug, info, warn) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_gdscript_fileA | Analyze a GDScript file and extract its structure (classes, functions, signals, variables, enums). Returns a comprehensive overview without reading the entire file into context. |
| get_gdscript_structureA | Get a high-level structure view of a GDScript file, showing all classes, functions, signals, and variables with their line numbers. |
| find_gdscript_symbolC | Search for a specific symbol (class, function, signal, etc.) in a GDScript file and get its details. |
| get_gdscript_dependenciesB | Extract dependencies from a GDScript file (extends, preload, import statements). |
| analyze_gdscript_codeB | Analyze GDScript code provided directly and extract its structure. |
| set_project_rootB | Set the project root directory to enable project-wide analysis. This will index all .gd files in the project. |
| get_project_rootA | Get the current project root directory and count of indexed GDScript files. |
| find_referencesB | Find all references to a symbol across the project or in a specific file. |
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 8 tools
The tools have overlapping purposes that could cause confusion, such as analyze_gdscript_code vs. analyze_gdscript_file vs. get_gdscript_structure, which all seem to extract code structure but with subtle differences in input or output. However, descriptions help clarify some distinctions, like find_gdscript_symbol being for specific symbols versus find_references for broader usage tracking.
All tool names follow a consistent snake_case pattern with clear verb_noun combinations (e.g., analyze_gdscript_code, find_gdscript_symbol, get_gdscript_dependencies). There are no deviations in naming style, making the set predictable and easy to parse.
With 8 tools, the count is well-scoped for a GDScript code analyzer, covering analysis, searching, dependency tracking, and project management. Each tool appears to serve a distinct role without unnecessary bloat, fitting typical expectations for this domain.
The tool set provides strong coverage for static analysis tasks in GDScript, including code structure extraction, symbol lookup, reference tracking, and project setup. A minor gap exists in dynamic or runtime analysis capabilities, but core workflows for code understanding are well-supported.