Skip to main content
Glama

Promote application

promote_application
Destructive

Promote the build one environment has proven onto the next: moves exactly the image tag the source environment runs onto the target environment through the ordinary deploy - never a rebuild, never configuration. Refused, in one sentence each, when the source is not healthy or its build cannot be identified, when the target follows pushes (turn that off first - the push loop would undo the promotion), when the target has a deploy in flight, or when a required secret has no value. Answers already_current with no deploy when the target already runs the build. Environments are named by id, cluster name or role (staging, production); a role two environments share needs the cluster name.

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>",
      "source_environment": "<source_environment>",
      "target_environment": "<target_environment>"
    },
    "name": "promote_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.
source_environmentYesThe environment that proved the build: its id, its cluster name, or its role.
target_environmentYesThe environment to carry the build onto: its id, its cluster name, or its role.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag a destructive, non-idempotent write, and the description adds real context on top: precisely what is mutated (only the image tag), what is deliberately not touched, the full set of refusal conditions, and the already_current short-circuit that performs no deploy. That is materially more than the annotations convey.

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 the core action and the 'never a rebuild, never configuration' constraint, then the failure modes, then the naming rule. It is dense and a few clauses stack awkwardly ('Refused, in one sentence each, when...'), but almost nothing is 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 three-parameter mutation with no output schema, it covers preconditions, failure modes, and the already_current outcome well enough to call correctly. It stops short of describing what a successful promotion response contains or how to verify the result afterward.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds semantics the schema lacks: environments may be addressed by id, cluster name, or role, and when two environments share a role the cluster name is required. It also assigns directionality (source proved the build, target carries it), which the schema descriptions only loosely imply.

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 and nails the mechanism: it moves exactly the image tag the source environment runs onto the target through the ordinary deploy, explicitly excluding rebuild and configuration changes. That contrast lets an agent separate this from a plain deploy_application call without opening either schema.

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 thorough when-not list: unhealthy source, unidentifiable build, target following pushes (with the remediation 'turn that off first'), deploy in flight, and missing secret values. It also names the no-op path (answers already_current when the target already runs the build) and the environment-naming disambiguation rule, so preconditions are checkable before invocation.

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.