engineering-matrix-explorer
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 |
|---|---|
| list_categoriesA | List all engineering tool categories with tool counts |
| search_engineering_matrixB | Search for engineering tools by name, tag, or use case. Supports multi-word queries. |
| get_repository_boilerplateA | Get starter boilerplate files for a specific tool or framework |
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 3 tools
Each tool targets a distinct function: retrieving boilerplate, listing categories, and searching the matrix. No overlap in purpose.
All tools follow a consistent verb_noun pattern using snake_case, making their actions and targets clear.
With 3 tools, the surface is somewhat minimal but covers the core exploratory functions for an engineering matrix. Could benefit from a tool to get details on a specific tool, but not a major issue.
The set provides search, categorization, and boilerplate retrieval, which are central to exploring a matrix. Missing a direct 'get tool details' function, but search may cover that need.