Aegis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AEGIS_MASTER_KEY | Yes | Master encryption key for the credential vault |
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 |
|---|---|
| aegis_proxy_requestB | Make an authenticated API call through Aegis. Credentials are injected automatically — you never see them. Provide the service name and API path; Aegis handles authentication. |
| aegis_list_servicesA | List all available services registered in Aegis. Returns service names, auth types, and allowed domains — never secrets. |
| aegis_healthB | Check the health status of Aegis, including credential and agent counts. |
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 clearly distinct purpose: health monitoring, service listing, and proxying requests. There is no overlap in functionality, and an agent can easily differentiate between them based on their specific roles.
All tool names follow a consistent 'aegis_' prefix with descriptive snake_case suffixes (health, list_services, proxy_request). This pattern is uniform across all tools, making them predictable and easy to understand.
With only 3 tools, the server feels minimal for a service management system like Aegis. While the tools cover basic operations, the scope might be too thin, potentially lacking advanced management features like service registration or configuration updates.
The tools provide core functionality for health checks, service listing, and proxying requests, but there are notable gaps. For example, there are no tools for managing services (e.g., adding or removing services) or handling authentication configurations, which could limit agent workflows in a service management context.