aegis-crew
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kb_search_toolC | Search the knowledge base; returns the top-k matching chunk texts. |
| read_doc_toolA | Read a single document from the authorized corpus and return its text. |
| publish_report_toolC | Write a report to an authorized output path; returns the path written. |
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 has a distinct purpose: searching the knowledge base, reading a document, and publishing a report. There is no overlap or ambiguity.
All tools use snake_case and include a verb, but the pattern varies: kb_search_tool follows noun_verb_tool, while read_doc_tool and publish_report_tool follow verb_noun_tool. This minor inconsistency is still clear.
With three tools, the set is minimal but fits a focused knowledge base and report creation workflow. It is not overly small given the scope.
The tools cover search, read, and publish, but lack update, delete, or list operations. For a basic workflow it is functional, but gaps exist for lifecycle management.