Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_playbookC

Run an Ansible playbook

list_inventoryC

List Ansible inventory hosts and groups

check_syntaxA

Check syntax of an Ansible playbook without executing it

list_tasksC

List all tasks that would be executed by a playbook

run_ad_hocC

Run an Ansible ad-hoc command against specified hosts

vault_encrypt_stringC

Encrypt a string using Ansible Vault

vault_decrypt_stringC

Decrypt a string encrypted with Ansible Vault

aws_ec2C

Manage AWS EC2 instances (list, create, start, stop, terminate)

aws_s3C

Manage AWS S3 buckets and objects

aws_vpcC

Manage AWS VPC networks

aws_cloudformationC

Manage AWS CloudFormation stacks

aws_iamC

Manage AWS IAM roles and policies

aws_rdsC

Manage AWS RDS database instances

aws_route53C

Manage AWS Route53 DNS records and zones

aws_elbC

Manage AWS Elastic Load Balancers

aws_lambdaC

Manage AWS Lambda functions

aws_dynamic_inventoryC

Create AWS dynamic inventory

terraformC

Execute Terraform commands (init, plan, apply, destroy, validate, output, etc.)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.9/5.0

Scored across 18 tools

Disambiguation4/5

The tools are clearly organized into AWS service management (e.g., aws_ec2, aws_s3), Ansible operations (e.g., run_playbook, list_inventory), and Terraform/Vault utilities, with minimal overlap. However, aws_cloudformation and terraform both handle infrastructure-as-code, which could cause slight confusion in selection, though their descriptions clarify distinct purposes.

Naming Consistency4/5

Most tools follow a consistent snake_case pattern with clear verb_noun or service_action naming (e.g., aws_ec2, run_playbook, vault_encrypt_string). The main deviation is 'terraform', which lacks a verb prefix, but this is minor given its distinct domain and common usage.

Tool Count4/5

With 18 tools, the count is reasonable for the broad scope of cloud infrastructure and automation management, covering AWS, Ansible, Terraform, and Vault. It might feel slightly heavy, but each tool addresses a specific, necessary function without obvious redundancy.

Completeness5/5

The toolset provides comprehensive coverage for cloud infrastructure operations: AWS services have full lifecycle management (e.g., create, list, manage), Ansible includes playbook execution, syntax checking, and inventory handling, and Terraform/Vault cover essential commands. No significant gaps are apparent for the intended domain.