Skip to main content
Glama

Deploy application

deploy_application
Destructive

Deploy an Application's built chart onto a cluster: creates or updates the installation in the given namespace. Requires a published build. Check the application's existing installations first (list_application_installations). Name the target by cluster_id or by environment (id, cluster name or role) - exactly one of the two. A redeploy re-applies the same manifests, so to recover a pod stuck on a missing Secret or ConfigMap propose it only when an earlier apply failed for a cause that has since cleared (such as an admission webhook that was still starting), and say so in the proposal.

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>"
    },
    "name": "deploy_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNoOptional deploy input values (non-secret).
namespaceNoTarget namespace (defaults to the application's name).
cluster_idNoUUID of the target cluster. Pass this or environment, never both.
deploy_modeNoOptional deploy mode passed through to the deploy lane.
environmentNoThe target environment named the way a person names it: its id, its cluster name, or its role (staging, production). Pass this or cluster_id, never both.
application_idYesThe Application's id.
prepare_databaseNoSet the application's database up for this deploy: when it declares PostgreSQL and the target cluster has no CloudNativePG operator, install Ankra's operator stack there first. Same as Set up the database on the deploy form and ankra ship --set-up-database. Needs stacks.write on the cluster. Pass it after a deploy was refused for the missing operator, or when the user asked for the database to be set up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / prepare_database
      Added value: +{
      +  "description": "Set the application's database up for this deploy: when it declares PostgreSQL and the target cluster has no CloudNativePG operator, install Ankra's operator stack there first. Same as Set up the database on the deploy form and ankra ship --set-up-database. Needs stacks.write on the cluster. Pass it after a deploy was refused for the missing operator, or when the user asked for the database to be set up.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description goes further by explaining that a redeploy re-applies the same manifests and is unsafe for a pod stuck on a missing Secret/ConfigMap. It adds an auth requirement ('Needs stacks.write on the cluster') for the prepare_database path that annotations cannot express.

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?

Purpose and prerequisite are front-loaded, then the target-selection rule, then the redeploy caveat. The final redeploy sentence is long and nested, but every clause carries an operational constraint rather than filler.

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 with no output schema, the description covers prerequisites, verification-by-listing, target selection, and the risky redeploy case. It stops short of describing what a successful deploy returns or the final state the agent should confirm.

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 parameter meaning is largely already documented. The description restates the mutually exclusive cluster_id/environment choice (already in the schema) but says nothing about deploy_mode or inputs beyond what the schema provides, so it adds little beyond 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 opens with a specific verb and resource ('Deploy an Application's built chart onto a cluster') and clarifies the effect ('creates or updates the installation in the given namespace'). This distinguishes it from siblings like promote_application or park_application_deployment without naming them, since it is clearly about initiating an install.

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?

It states the prerequisite ('Requires a published build'), instructs the agent to check existing state first via list_application_installations, and gives a concrete when-not for redeploys ('propose it only when an earlier apply failed for a cause that has since cleared'). It also names the exact condition for prepare_database ('after a deploy was refused for the missing operator').

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.