k8scortex-mcp

create_job

Create a Kubernetes Job using basic configuration with image and command, or a full YAML manifest. Supports dry-run simulation.

Instructions

Creates a new Job. Use either basic configuration or provide a raw YAML manifest.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "namespace": "<namespace>"
    },
    "name": "create_job"
  }
}

Input Schema

Name	Required	Description
`image`	No	Container image to run (if using basic config)
`dryRun`	No	If true, simulates the action without making changes
`cluster`	No	Target cluster name (default: 'default')
`command`	No	Command to run (if using basic config)
`jobName`	No	The name of the job to create
`namespace`	Yes	The Kubernetes namespace
`yamlManifest`	No	Full YAML manifest for advanced job creation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 28, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are present, so the description must disclose all behavioral traits. It mentions creation but does not disclose what happens if the job already exists, permission requirements, side effects, or defaults (e.g., dryRun=true). This lack of detail limits transparency.

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?

A single sentence that front-loads the purpose. It is concise without wasted words. However, it could be slightly expanded to include key behavioral details 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 7 parameters, no output schema, and no annotations, the description is too brief. It does not explain what happens when both basic and YAML manifest are provided, the effect of dryRun, or the return behavior. For a creation tool, more context is needed for complete understanding.

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 high-level context about two modes but does not provide new meaning beyond the parameter descriptions. The schema already includes conditional notes (e.g., 'if using basic config'). The description reinforces this but does not significantly enhance understanding.

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

Purpose5/5

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

The description clearly states 'Creates a new Job', specifying the resource 'Job'. It distinguishes from sibling tools like create_deployment by naming the resource and mentioning two configuration modes (basic vs YAML manifest), so the purpose is specific and differentiated.

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

Usage Guidelines3/5

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

The description says 'Use either basic configuration or provide a raw YAML manifest', which implies two usage patterns but does not explain when to choose one over the other or when not to use this tool. No comparison to other creation tools (e.g., create_deployment) is given, so guidance is minimal.

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

Deploy Server