k8scortex-mcp

suspend_flux_resource

Suspend reconciliation of a Flux Kustomization or HelmRelease to pause automated Kubernetes deployments. Provide resource type, namespace, and name.

Instructions

Suspends reconciliation of a Flux Kustomization or HelmRelease to pause automated deployments.

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": "suspend_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 exist, so the description must carry the full burden. It states the action ('suspends reconciliation') but does not disclose side effects, reversibility, required permissions, or rate limits. For a state-modifying tool, this is insufficient.

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?

The description is a single, clear sentence that is appropriately concise. It is front-loaded with the action. However, it could benefit from slightly more structure (e.g., listing the resource types explicitly).

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?

Given the tool's complexity (5 parameters, all documented) and no output schema, the description adequately explains the core purpose but lacks completeness in usage guidance and behavioral context. It is minimally viable.

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 the schema already documents all parameters. The description adds no additional semantic value beyond what is in the schema, meeting the baseline.

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 uses a specific verb ('Suspends reconciliation') and clearly identifies the target resources ('Flux Kustomization or HelmRelease') and the effect ('pause automated deployments'). It effectively distinguishes this tool from its sibling 'resume_flux_resource'.

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 implies usage for pausing automated deployments but lacks explicit guidance on when to use versus alternatives or when not to use. No context about prerequisites or exclusions is provided.

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

Deploy Server