@alex-apps/ng-token-saver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NG_TOKEN_SAVER_IDLE_MS | No | A language-server session unused this long shuts its ngserver down, and the next call pays the cold start again. Default 900000 (15 minutes); 0 keeps sessions alive until the server exits. A session with a call in flight is never shut down. | 900000 |
| NG_TOKEN_SAVER_SERVERS_DIR | No | Where the language-server branch lives, if not in tools/servers next to the build. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ng_template_definitionA | From a position in an Angular template (.html or inline in .ts) to its TypeScript declaration. line and character are 0-based, as in LSP. |
| ng_template_diagnosticsC | Angular compiler errors for a template after an edit. Accepts .html or .ts; files checks a batch. An entry anchored in the companion file names it in file. An empty list means "no errors" only when the server is healthy. |
| ng_component_infoA | Public contract of a component or directive: inputs, outputs, class members, decorator metadata. Accepts .ts or .html. Reads the source; ngserver is not needed. |
| ng_workspace_mapA | Workspace projects, Angular/CLI/TypeScript versions, strictTemplates and zone.js per project. Understands angular.json, Nx and solution style. Call once per session. |
| ng_version_rulesB | What exists and what does not in this project's Angular version: template syntax, signal APIs, zoneless, DI. Every rule was measured on the v17-v22 stand. |
| ng_find_usagesA | Usages of a component, directive, pipe or service across the workspace: elements, attribute selectors, pipes and class references. Accepts a file path or a selector. |
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 targets a distinct aspect of Angular development: component metadata, template positions, template diagnostics, workspace configuration, version-specific rules, and cross-reference usages. There is no overlap or ambiguity between them.
All tools follow a consistent 'ng_' prefix with snake_case names that clearly indicate their purpose. The naming pattern is uniform across all six tools, making it easy to predict tool functionality from the name alone.
With exactly six tools, the server is appropriately scoped for Angular code analysis. Each tool serves a distinct purpose without redundancy, and the count is within the ideal range.
The tool set covers the core workflows for Angular analysis: understanding components, navigating from templates to definitions, checking diagnostics, mapping workspace structure, understanding version features, and finding usages. Minor gaps like batch processes are addressed by the batch capability in diagnostics, and the set feels complete for a read-only analysis server.