k8s-mcp

k8s_apply

Apply YAML manifests to create or patch Kubernetes Deployments and ConfigMaps.

Instructions

Create or patch a Deployment or ConfigMap from YAML.

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": {
      "manifest_yaml": "<manifest_yaml>"
    },
    "name": "k8s_apply"
  }
}

Input Schema

Name	Required	Description	Default
`session_name`	No		default
`manifest_yaml`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 24, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It discloses that the tool mutates resources ('Create or patch'), but fails to mention that it requires an active connection, how it handles existing resources, whether it is idempotent, or what errors might occur. The behavior beyond the core action is opaque.

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

Conciseness5/5

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

The description is a single, compact sentence with no filler. It front-loads the action and resource scope, making it immediately scannable. Every word contributes to the core purpose.

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 mutation tool with no annotations and a 0% schema coverage, the description is severely incomplete. It omits session_name semantics, connection prerequisites, YAML format expectations, and success/failure behavior. An agent would struggle to use it correctly without additional information, despite having an output schema.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It clarifies that manifest_yaml is the YAML content, but it does not explain session_name at all. The agent is left guessing the purpose of session_name, and the description adds minimal value beyond what the parameter names imply.

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 states a specific verb ('Create or patch') and resource types ('Deployment or ConfigMap'), clearly distinguishing it from siblings like k8s_scale, k8s_restart, and k8s_delete_pod. It is immediately evident what this tool does and how it differs from other operations.

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?

The description gives no guidance on when to use this tool versus alternatives, no mention of prerequisites like being connected to a cluster, and no exclusions or conditions. It only states capability, leaving usage context entirely to inference.

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

Deploy Server