k8scortex-mcp

resume_cronjob

Resume a suspended Kubernetes CronJob in a specified namespace and cluster, with optional dry-run to simulate the action without making changes.

Instructions

Resumes a suspended CronJob.

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>",
      "cronJobName": "<cronJobName>"
    },
    "name": "resume_cronjob"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true, simulates the action without making changes
`cluster`	No	Target cluster name (default: 'default')
`namespace`	Yes	The Kubernetes namespace
`cronJobName`	Yes	The name of the CronJob to resume

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 28, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations exist, so description must disclose behavioral traits. It only states the action, omitting prerequisites (CronJob must be suspended), dry-run behavior (despite parameter), side effects, and reversibility.

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, no wasted words. Could benefit from structured format (e.g., bullets for parameters), but acceptable for a simple action.

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?

No output schema and description lacks information on return values, error conditions, or immediate vs scheduled resumption. Insufficient for complex decision-making.

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 covers all 4 parameters with individual descriptions. The description adds no additional meaning beyond the schema, earning baseline 3.

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?

Description clearly states verb 'Resumes' and resource 'suspended CronJob', differentiating it from sibling 'suspend_cronjob'. The action is unambiguous.

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 (e.g., when CronJob is already running, or after suspend_cronjob). Agent must infer context from name alone.

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

Deploy Server