kubopt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KUBEOPT_API_URL | Yes | URL of your KubeOpt instance | |
| KUBEOPT_PASSWORD | Yes | KubeOpt password | |
| KUBEOPT_USERNAME | Yes | KubeOpt username |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clustersA | List all Kubernetes clusters being monitored with their latest cost and optimization data |
| get_cost_summaryA | Get portfolio-level cost summary across all clusters |
| get_cluster_analysisA | Get detailed cost analysis for a specific cluster including cost breakdown, resource utilization, node recommendations, and anomaly detection |
| get_recommendationsB | Get actionable optimization recommendations for a cluster, sorted by estimated savings impact |
| analyze_clusterA | Trigger a fresh cost analysis for a cluster. This runs in the background and takes 1-15 minutes depending on cluster size and cloud provider. Polls for completion and returns the results. |
| get_pod_costsB | Get per-pod cost breakdown for a cluster, useful for identifying expensive workloads. Optionally filter by namespace. |
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 6 tools
Each tool has a clearly distinct purpose: triggering analysis, retrieving cluster-level results, portfolio summary, pod-level costs, recommendations, and listing clusters. No overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern (e.g., analyze_cluster, get_cluster_analysis, list_clusters), making them predictable and easy to distinguish.
Six tools is well-scoped for a Kubernetes cost analysis server, covering the core workflows without being excessive or insufficient.
The tool surface covers the full lifecycle: triggering analysis, retrieving detailed results (cluster, pod, portfolio), recommendations, and listing—no obvious gaps for the stated purpose.