Skip to main content
Glama

Park application deployment

park_application_deployment
Destructive

Park one deployment of an Application: scale its workload to zero replicas ON PURPOSE, remembering the prior replica count so wake_application_deployment can restore it. Parked is a deliberate rest, never 'not deployed' - the installation, its manifests and its published Ingress host all stay, and the application's deployment_state reads 'parked'. Use list_application_installations or get_application_deployments first to find the cluster and namespace. Refused with a conflict when the deployment is already parked. This does NOT uninstall or delete anything.

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": {
      "application_id": "<application_id>",
      "cluster_id": "<cluster_id>",
      "namespace": "<namespace>"
    },
    "name": "park_application_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceYesNamespace the deployment runs in (part of the deployment's identity - one application can be deployed twice on one cluster).
cluster_idYesUUID of the cluster the deployment runs on.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the installation, manifests and published Ingress host survive, the prior replica count is persisted for restoration, deployment_state reads 'parked', and an already-parked deployment returns a conflict. This meaningfully reframes the destructiveHint=true flag by clarifying that nothing is uninstalled or deleted — a clarification, not a contradiction, since scaling to zero is still a disruptive write.

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?

Front-loaded with purpose, then constraints, then the discovery hint and the non-destructive caveat — a sensible ordering with no filler sentences. The emphasized 'ON PURPOSE' is slightly rhetorical, but overall the density is justified.

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

Completeness5/5

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

For a three-parameter mutation with no output schema, the description covers the mechanism, the observable state change, the conflict behavior, and what is preserved. Nothing an agent needs to invoke it safely and correctly is missing.

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%, so all three parameters are already documented, including the namespace-as-identity note. The description only reinforces that cluster and namespace must be discovered first; it adds little syntax or format meaning beyond the schema.

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 ('Park one deployment of an Application') plus the exact mechanism (scale workload to zero, remembering the prior replica count). It explicitly separates itself from wake_application_deployment (restore), from uninstall/delete ('This does NOT uninstall or delete anything'), and from a non-deployed state.

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 a prerequisite discovery path ('Use list_application_installations or get_application_deployments first to find the cluster and namespace') and names the counterpart tool that undoes the action. It also documents the failure condition (refused with a conflict when already parked), which tells the agent when NOT to call.

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.