Skip to main content
Glama
Flux159
by Flux159

kubectl_create

Create Kubernetes resources from YAML manifests or defined subcommands. Supports deployments, services, configmaps, secrets, and more with dry-run and schema validation 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?

No annotations are provided, so the description carries the full burden. It only states 'create' without disclosing side effects, required permissions, failure modes, or whether existing resources are updated or replaced. This is insufficient for a mutation-oriented tool.

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, but it is vague and lacks structure. It is not overly long, but it does not efficiently convey key information. It could be more concise while providing more value.

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?

The tool has 22 parameters and no output schema, yet the description does not explain how parameters interact, what return values look like, or provide examples. For a complex tool, this is incomplete. No guidance on common use cases.

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 the schema already documents all 22 parameters. The description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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

Purpose3/5

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

The description states 'Create Kubernetes resources' which is clear verb+resource, but the mention of 'using various methods (from file or using subcommands)' is vague. It fails to differentiate from sibling tool kubectl_apply, which also creates resources. The purpose is clear at a high level but lacks specificity.

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 over alternatives like kubectl_apply or when to choose file-based vs subcommand-based creation. The description does not mention prerequisites, context, or when not to use it.

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/Flux159/mcp-server-kubernetes'

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