mctl
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mctl_connection_infoB | Get information on how to connect to the full mctl AI-native Kubernetes platform. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or deviations.
One tool is too few for a server named 'mctl' that suggests a Kubernetes platform, implying a broader scope that likely requires more operations like managing resources, deployments, or clusters.
The tool surface is severely incomplete for a Kubernetes platform; it only provides connection info, lacking any CRUD or lifecycle operations for managing Kubernetes resources, which are essential for such a domain.