k8s-interactive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| run_kubectl_commandC | Run a kubectl command against the cluster pointed to by the current kubeconfig |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_notes | Summarize all notes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| First Note | A text note: First Note |
| Second Note | A text note: Second Note |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as running kubectl commands, making it impossible for an agent to confuse it with another tool.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'run_kubectl_command' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
A single tool is too few for a Kubernetes management server, as it lacks coverage for common operations like listing resources, applying configurations, or checking cluster status. This forces agents to rely solely on raw kubectl commands, which is inefficient and error-prone for the domain.
The tool surface is severely incomplete for Kubernetes management. While 'run_kubectl_command' provides a generic entry point, it lacks dedicated tools for essential operations such as get, apply, delete, describe, or logs, leaving significant gaps that will cause agent failures in automated workflows.