Skip to main content
Glama

Apply manifest

apply_manifest
Destructive

Apply a Kubernetes manifest (YAML) to create or update resources. Supports any Kubernetes resource type. For resources managed by a stack, prefer add_manifest_to_draft + apply_stack_changes. Direct apply_manifest on ArgoCD-managed resources is rejected unless allow_bypass=true.

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": "<manifest>",
      "cluster_id": "<cluster_id>"
    },
    "name": "apply_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, preview the change without executing it.
manifestYesYAML manifest content to apply.
namespaceNoDefault namespace for namespaced resources without explicit namespace.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
allow_bypassNoBypass the ArgoCD-managed-resource safety check. Set ONLY when the user explicitly asked to override ArgoCD (e.g. 'force', 'bypass argo'). The confirmation dialog still appears with an enhanced warning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses the ArgoCD-managed-resource safety gate and the rejection behavior, which the agent could not infer from structured fields. It does not describe execution mechanics such as whether the apply is asynchronous or what confirmation flow follows, so it stops short of full transparency.

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?

Three sentences, front-loaded with the core action, then alternatives, then the safety constraint. No filler and each sentence carries distinct routing or behavioral information.

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

Completeness4/5

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

For a destructive, non-idempotent mutation tool with full annotation and parameter coverage, the description covers purpose, alternatives and guardrails. The one gap is the outcome of the call — whether it returns an execution to wait on — which matters given siblings like wait_for_execution and list_recent_executions.

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 all five parameters including dry_run, namespace, cluster_id and allow_bypass are already documented. The description only reinforces allow_bypass by tying it to the ArgoCD rejection rule; it adds no format or interaction detail beyond the schema, so the baseline of 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?

States a specific verb and resource ('Apply a Kubernetes manifest (YAML)') plus the effect ('create or update resources') and scope ('Supports any Kubernetes resource type'). It also names the sibling path for stack-managed resources, so the agent can distinguish it from add_manifest_to_stack_profile_draft and apply_stack_changes without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: for stack-managed resources prefer add_manifest_to_draft + apply_stack_changes. It also states the hard exclusion — direct apply on ArgoCD-managed resources is rejected unless allow_bypass=true — so when-not-to-use and the escape hatch are both spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.