Skip to main content
Glama
ACRT-EVAL
by ACRT-EVAL

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
list_podsC

List pods in a namespace

list_deploymentsC

List deployments in a namespace

list_servicesB

List services in a namespace

list_namespacesB

List all namespaces

create_podC

Create a new Kubernetes pod

create_deploymentC

Create a new Kubernetes deployment

delete_podC

Delete a Kubernetes pod

describe_podB

Describe a Kubernetes pod (read details like status, containers, etc.)

cleanupC

Cleanup all managed resources

list_nodesB

List all nodes in the cluster

get_logsC

Get logs from pods, deployments, jobs, or resources matching a label selector

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Kubernetes PodsList of pods in the default namespace
Kubernetes DeploymentsList of deployments in the default namespace
Kubernetes ServicesList of services in the default namespace
Kubernetes NamespacesList of all namespaces
Kubernetes NodesList of all nodes in the cluster

TDQS

B3/5.0

Scored across 11 tools

Disambiguation4/5

Each tool targets a distinct resource+action combination (list vs create vs delete vs describe on separate resources). get_logs overlaps conceptually with list/describe since it spans multiple resource types, but its purpose is clear enough to avoid misselection.

Naming Consistency4/5

Strong verb_noun pattern (list_pods, create_pod, delete_pod, describe_pod, list_nodes). The lone outlier is 'cleanup', which lacks a verb_noun structure and is vaguer than the rest, and get_logs uses 'get' rather than the dominant 'list'.

Tool Count5/5

Eleven tools is well-scoped for a Kubernetes management server, covering listing, creation, deletion, inspection, logs, and cleanup without bloat.

Completeness3/5

Coverage is asymmetric: deployments can be created but not deleted, and there's no describe for deployments or services despite describe_pod existing. Pods have full list/create/delete/describe/logs lifecycle, but the broader surface has notable gaps that could cause agent dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues