Skip to main content
Glama
htrixtec

MCP Server Kubernetes

by htrixtec

kubectl_create

Create Kubernetes resources via YAML files or subcommands, with dry-run and output format options.

Instructions

Create Kubernetes resources using various methods (from file or using subcommands)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, only validate the resource, don't actually execute the operation
outputNoOutput format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-fileyaml
validateNoIf true, validate resource schema against server schema
manifestNoYAML manifest to create resources from
filenameNoPath to a YAML file to create resources from
resourceTypeNoType of resource to create (namespace, configmap, deployment, service, etc.)
nameNoName of the resource to create
namespaceNoKubernetes namespacedefault
fromLiteralNoKey-value pair for creating configmap (e.g. ["key1=value1", "key2=value2"])
fromFileNoPath to file for creating configmap (e.g. ["key1=/path/to/file1", "key2=/path/to/file2"])
secretTypeNoType of secret to create (generic, docker-registry, tls)
serviceTypeNoType of service to create (clusterip, nodeport, loadbalancer, externalname)
tcpPortNoPort pairs for tcp service (e.g. ["80:8080", "443:8443"])
imageNoImage to use for the containers in the deployment
replicasNoNumber of replicas to create for the deployment
portNoPort that the container exposes
scheduleNoCron schedule expression for the CronJob (e.g. "*/5 * * * *")
suspendNoWhether to suspend the CronJob
commandNoCommand to run in the container
labelsNoLabels to apply to the resource (e.g. ["key1=value1", "key2=value2"])
annotationsNoAnnotations to apply to the resource (e.g. ["key1=value1", "key2=value2"])
contextNoKubeconfig Context to use for the command (optional - defaults to null)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden for behavioral disclosure. It only mentions creation methods but fails to disclose important behavior like dry-run support (available in schema), required permissions, error handling, or side effects. The description is too terse to be transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise. However, it is too brief and sacrifices clarity; it could be expanded to cover the two methods and key parameters without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite high parameter count (22) and no output schema, the description is extremely brief. It does not explain the two creation methods, parameter interactions, or typical usage patterns. For a tool of this complexity, much more detail is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it only hints at two methods without elaborating how parameters correspond. No additional value is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Create' and the resource 'Kubernetes resources', and mentions two methods (from file or subcommands). However, it does not distinguish this tool from the sibling tool 'kubectl_apply', which also creates resources. A more specific description would highlight the imperative nature vs declarative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool instead of alternatives like kubectl_apply or kubectl_patch. There is no mention of prerequisites, preferred use cases, or exclusions. The description only states the tool creates resources without any contextual decision help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/htrixtec/mcp-server-kubernetes'

If you have feedback or need assistance with the MCP directory API, please join our Discord server