stack-advisor
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 |
|---|---|
| recommend_stackA | Describe your project and get 1-3 recommended tech stacks with reasoning, tradeoffs, and what each layer should use. |
| list_stacksA | List all available stack templates with their tags |
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 lists available stack templates, the other provides personalized recommendations. There is no overlap or ambiguity.
Both tool names follow the same verb_noun pattern in snake_case (list_stacks, recommend_stack), maintaining perfect consistency.
With only 2 tools, the surface is too thin for a 'stack advisor' server. Users likely need additional functionality like searching, filtering, or viewing stack details.
Obvious gaps exist: no way to inspect individual stack templates, search by tags, compare stacks, or manage stacks. The surface is severely limited for the domain.