k8scortex-mcp

resume_flux_resource

Resume suspended Flux Kustomization or HelmRelease reconciliation. Specify resource type, namespace, and name, with optional dry-run.

Instructions

Resumes reconciliation of a suspended Flux Kustomization or HelmRelease.

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": {
      "resourceType": "<resourceType>",
      "namespace": "<namespace>",
      "name": "<name>"
    },
    "name": "resume_flux_resource"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name of the resource
`dryRun`	No	If true, simulates the action
`cluster`	No	Target cluster name (default: 'default')
`namespace`	Yes	Namespace of the resource
`resourceType`	Yes	'kustomization' or 'helmrelease'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 28, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided. Description only says 'resumes reconciliation', which signals a write operation, but does not disclose side effects, prerequisites (resource must be suspended), or potential consequences. Burden not fully met.

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 concise sentence. Efficient but could benefit from a bit more context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple action tool, but no output schema and no mention of dryRun behavior (though dryRun is in schema). Could be more complete regarding suspended state requirement.

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% with each parameter described. Description adds no additional meaning beyond the schema, so baseline 3 applies.

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 the verb 'resumes' and the target resources 'suspended Flux Kustomization or HelmRelease'. It distinguishes itself from sibling tools like suspend_flux_resource and list tools.

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?

No explicit guidance on when to use or alternatives. Implies usage after suspension, but lacks prerequisites or exclusions. Context from sibling names helps but not explicit.

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

Deploy Server