Generate Tech Stack
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_tech_stackA | Scan a project directory and generate a TECH_STACK.html visual page. Includes a stat row, layered architecture diagram, bar chart summary, and colour-coded tool cards. Detects languages, frameworks, databases, AI SDKs, testing, observability, security, and infrastructure tools. |
| list_tech_stackA | Scan a project and return the tech stack as structured JSON (no HTML file written). Good for programmatic use. |
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 2 tools
The two tools have clearly distinct purposes: one generates a visual HTML report, the other returns structured JSON for programmatic use. No overlap in functionality.
Both tools use 'tech_stack' noun consistently, but the verbs differ ('generate' vs 'list') which is a minor inconsistency. Mostly follows verb_noun pattern.
Two tools are appropriate for the narrow domain of detecting and outputting a tech stack. The pair covers the essential use cases without unnecessary bloat.
The tools cover both visual and data-driven outputs, which are the primary needs for tech stack generation. No obvious gaps for the stated purpose.