AWS Sage
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_PROFILE | No | AWS profile to use | default |
| AWS_DEFAULT_REGION | No | Default AWS region | us-east-1 |
| AWS_SAGE_SAFETY_MODE | No | Safety mode (read_only/standard/unrestricted) | read_only |
| AWS_SAGE_LOCALSTACK_HOST | No | LocalStack host | localhost |
| AWS_SAGE_LOCALSTACK_PORT | No | LocalStack port | 4566 |
| AWS_SAGE_LOCALSTACK_ENABLED | No | Enable LocalStack by default | false |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_profilesA | List all available AWS profiles |
| select_profileC | Select an AWS profile to use for operations |
| get_account_infoA | Get current AWS account and session information |
| set_safety_modeC | Change the safety mode for operations |
| aws_queryC | Execute read-only AWS queries (natural language supported) |
| aws_executeD | Execute AWS operations (requires appropriate safety mode) |
| validate_operationA | Check if an operation is valid and allowed without executing |
| get_contextB | Get current conversation context (recent resources, aliases) |
| set_aliasC | Create a shortcut alias for a resource |
| list_aliasesB | List all defined aliases |
| discover_resourcesC | Find resources across services by tags |
| search_docsC | Search AWS documentation for a service or topic |
| get_aws_knowledgeC | Get AWS best practices and operational knowledge |
| get_best_practicesC | Get best practices for an AWS service |
| get_service_limitsC | Get service quotas and limits for an AWS service |
| map_dependenciesC | Map resource dependencies and relationships |
| impact_analysisC | Analyze the impact of modifying or deleting a resource |
| investigate_incidentD | Run automated incident investigation workflow |
| find_idle_resourcesC | Find potentially idle or underutilized AWS resources |
| get_rightsizing_recommendationsC | Get recommendations for right-sizing EC2 and RDS instances |
| get_cost_breakdownC | Get cost breakdown by service or tag |
| project_costsC | Estimate costs for proposed AWS resources |
| list_environmentsA | List all configured AWS environments (production, localstack) |
| switch_environmentB | Switch between AWS environments (production or localstack) |
| get_environment_infoC | Get detailed information about the current AWS environment |
| check_localstackA | Check LocalStack connectivity and available services |
| compare_environmentsB | Compare resources between two AWS environments (e.g., localstack vs production) |
| assume_roleA | Assume an IAM role in another AWS account for cross-account access |
| list_accountsB | List all configured AWS accounts (including assumed roles) |
| switch_accountC | Switch the active AWS account context |
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 30 tools
Core operational tools like aws_query, aws_execute, and validate_operation are reasonably distinct, but several knowledge tools overlap (search_docs, get_aws_knowledge, get_best_practices). Profile/account tools (list_profiles, list_accounts, switch_account, select_profile) also have unclear boundaries.
Most tools use snake_case and many follow a verb_noun pattern, but the pattern is inconsistent: impact_analysis and aws_query/aws_execute break the action-first convention, and get_* is applied to very different concepts. It is readable but lacks a predictable system-wide pattern.
At 30 tools, the surface feels heavy and exceeds the range where each tool clearly earns its place. Several tools could be consolidated, such as the documentation/knowledge trio and the overlapping account/profile tools.
The tool set covers a broad AWS workflow: profiles, accounts, environments, safety controls, queries, cost analysis, incident investigation, and best practices. Minor gaps exist—no delete_alias or context reset—but generic aws_execute fills most operational needs.