Skip to main content
Glama
Flux159
by Flux159

kubectl_create

Create Kubernetes resources from YAML manifest, file, or subcommands with support for dry-run and validation.

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 provided; description only says 'Create' with no mention of side effects, idempotency, permissions, or what happens on success/failure. The dryRun parameter is in schema but not highlighted.

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?

Single sentence is concise, no fluff. Could benefit from structuring as bullet points or listing modes, but not overly 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?

For a tool with 22 parameters, no output schema, and no annotations, the description is too sparse. Missing return value info, error handling, and context on which parameters to use together.

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?

All 22 parameters have descriptions in the schema (100% coverage), so the description adds minimal value. It hints at two modes but does not synthesize parameter groups or provide usage patterns beyond schema.

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 action ('Create') and the resource ('Kubernetes resources'), and mentions two methods (from file or subcommands). It is distinct from siblings like 'kubectl_apply' which implies create-or-update, but does not explicitly differentiate.

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 on when to use this tool versus alternatives like 'kubectl_apply' or when to choose file-based vs subcommand-based creation. The description lacks decision-making context.

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