Skip to main content
Glama
Flux159
by Flux159

kubectl_create

Create Kubernetes resources using YAML files or subcommands for types like deployments, configmaps, and services. Includes dry-run and 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 must cover behavioral traits. It only states 'Create Kubernetes resources' without disclosing mutation behavior, error handling on existing resources, permission requirements, or side effects. The description is insufficient for an agent to understand safety implications.

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

Conciseness4/5

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

The description is a single sentence with 12 words, very concise. It is front-loaded but lacks detail. No wasted words, but could be expanded without losing conciseness.

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?

Given the tool's complexity (22 parameters, no output schema), the description is too minimal. It does not explain the two creation methods, parameter dependencies, or what the tool returns. An agent would need to infer everything from the schema alone, which is insufficient.

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 coverage is 100%, so the schema already documents all 22 parameters. The description adds no extra meaning beyond 'using various methods (from file or using subcommands)'. It doesn't clarify parameter interactions or required groupings. Baseline 3 is appropriate.

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 tool creates Kubernetes resources using files or subcommands, distinguishing it from siblings like kubectl_apply which is declarative. However, it could be more explicit about the imperative nature and the two distinct methods.

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 versus alternatives (e.g., kubectl_apply, kubectl_patch). There is no mention of prerequisites, when to avoid, or which parameters to combine for different resource types.

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