k8s-mcp-assistant
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 |
|---|---|
| k8s.app_statusC | dada un nombre de aplicacion, busca el estado de los pods |
| k8s.pod_logsB | Obtiene los logs de un pod específico en Kubernetes. Útil para debugging y troubleshooting. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| README.md | Archivo README del proyecto |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one checks pod status for an application, while the other retrieves logs for a specific pod. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tools follow a consistent naming pattern using 'k8s.' prefix and snake_case (app_status, pod_logs). This uniformity enhances readability and predictability across the tool set.
With only two tools, the server feels thin for a Kubernetes assistant domain, which typically involves more operations like scaling, deployment, or resource management. This limited scope may hinder agent workflows.
The tool set is severely incomplete for Kubernetes operations, lacking essential CRUD actions such as creating, updating, or deleting resources. Agents will face significant gaps when trying to perform common tasks in this domain.