k8scortex-mcp

sync_gitops_app

Force sync reconciliation of GitOps applications: ArgoCD, Flux Kustomization, or HelmRelease. Dry run mode available for simulation.

Instructions

Forces a sync/reconciliation of an ArgoCD Application, Flux Kustomization, or Flux 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": {
      "engine": "<engine>",
      "namespace": "<namespace>",
      "appName": "<appName>"
    },
    "name": "sync_gitops_app"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true, simulates the action
`engine`	Yes	GitOps engine ('argocd' or 'flux')
`appName`	Yes	The name of the application/kustomization/helmrelease
`cluster`	No	Target cluster name (default: 'default')
`namespace`	Yes	The namespace of the application/kustomization/helmrelease
`resourceType`	No	Flux only: 'kustomization' (default) or 'helmrelease'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Forces a sync/reconciliation' indicates a state-changing action, it does not elaborate on side effects, failure modes, necessary permissions, or rate limits. The description is insufficient for an agent to understand the tool's impact.

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 concise sentence that immediately conveys the action and scope. It is front-loaded with the key verb and follows with details, containing no redundancy or unnecessary words.

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?

For a tool with 6 parameters, 3 required, and no output schema, the description is minimal. It does not explain return behavior, error conditions, or how the tool interacts with the cluster state. While the core action is clear, additional context about post-sync behavior would improve completeness.

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 baseline is 3. The description adds no extra semantic context beyond what the schema already provides for parameters. It does not clarify parameter relationships or usage nuances, so it meets but does not exceed expectations.

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 'sync/reconciliation' and explicitly names the supported resources (ArgoCD Application, Flux Kustomization, Flux HelmRelease), making the tool's purpose clear and distinct from sibling tools that are primarily read-only or status-checking.

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 the tool is for forcing syncs but does not provide explicit guidance on when to use it versus alternatives (e.g., get_gitops_app_status). No mention of cases where it should not be used or prerequisites, leaving the agent to infer context.

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

Deploy Server