Skip to main content
Glama
abhijeetka
by abhijeetka

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_podsC

Get all pods in the specified namespace

get_failing_podsB

Get all pods with issues in the specified namespace

get_servicesC

Get all services in the specified namespace

describe_podC

Describe a specific pod

get_namespacesB

Get all namespaces in the cluster

get_nodesB

Get all nodes in the cluster

get_deploymentsC

Get all deployments in the specified namespace

get_jobsC

Get all jobs in the specified namespace

get_cronjobsC

Get all cronjobs in the specified namespace

get_statefulsetsC

Get all statefulsets in the specified namespace

get_daemonsetsC

Get all daemonsets in the specified namespace

expose_serviceC

Expose a resource as a new kubernetes service k8s_object can be pod (po), service (svc), replicationcontroller (rc), deployment (deploy), replicaset (rs) Type for this service: ClusterIP, NodePort, LoadBalancer, or ExternalName. Default is 'ClusterIP'.

port_forwardC

Port forward a resource to the outside world k8s_object can be a pod, deployment or a service and it should be in the format pod/, deployment/, service/

get_logsC

Get the logs of a specific pod

get_eventsC

Get the events of a specific namespace

create_deploymentB

Create a Kubernetes deployment with specified name, image, namespace and replicas

get_current_contextB

Get the current Kubernetes context

list_contextsB

List all available Kubernetes contexts

use_contextB

Switch to a specific Kubernetes context Args: context_name: The name of the Kubernetes context to switch to

annotate_resourceC

Annotate a Kubernetes resource with the specified annotation

Args:
    resource_type: Type of the resource (e.g., pod, service, deployment)
    resource_name: Name of the resource to annotate
    annotation: Annotation to add (e.g., key=value)
    namespace: Namespace of the resource
remove_annotationC

Remove an annotation from a Kubernetes resource

Args:
    resource_type: Type of the resource (e.g., pod, service, deployment)
    resource_name: Name of the resource to remove the annotation from
    annotation_key: Key of the annotation to remove
    namespace: Namespace of the resource
label_resourceA

Label a Kubernetes resource with the specified label

Args:
    resource_type: Type of the resource (e.g., pod, service, deployment)
    resource_name: Name of the resource to label
    label: Label to add (e.g., key=value)
    namespace: Namespace of the resource
remove_labelB

Remove a label from a Kubernetes resource

Args:
    resource_type: Type of the resource (e.g., pod, service, deployment)
    resource_name: Name of the resource to remove the label from
    label_key: Key of the label to remove
    namespace: Namespace of the resource
update_deploymentC

Update a Kubernetes deployment with new replicas count and/or image

Args:
    name: Name of the deployment to update
    namespace: Namespace of the deployment
    replicas: New number of replicas (optional)
    image: New container image (optional)
delete_resourceB

Delete a Kubernetes resource

Args:
    resource_type: Type of the resource (e.g., pod, service, deployment,configmap,secret,ingress,statefulset,replicaset,damonset,newtorkpolicy,rolebinding,role,serviceaccount,job,cronjob)
    resource_name: Name of the resource to delete
    namespace: Namespace of the resource

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 25 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific Kubernetes resources or operations, with clear boundaries like annotate_resource vs. remove_annotation. However, some overlap exists between get_pods and describe_pod, and expose_service and port_forward could be confused for similar networking tasks, though descriptions help differentiate them.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern throughout, such as get_pods, create_deployment, and delete_resource. Minor deviations include describe_pod (singular noun) and expose_service (which could be named create_service for consistency), but overall the pattern is predictable and readable.

Tool Count3/5

With 25 tools, the count feels heavy for a Kubernetes server, bordering on excessive. While Kubernetes is a complex domain, this many tools may overwhelm agents and could be streamlined, such as by consolidating get_* tools into a single generic get_resource with parameters.

Completeness5/5

The tool set provides comprehensive coverage of Kubernetes operations, including CRUD for deployments, resource management (annotate, label, delete), monitoring (get_logs, get_events), and cluster administration (context switching, namespace listing). No obvious gaps are present for core workflows, ensuring agents can handle most tasks without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues