Skip to main content
Glama

Set application auto deploy

set_application_auto_deploy
Destructive

Turn an Application's push-to-deploy switch on or off. With it on, a build the platform observes on the tracked branch is rolled out to the Application's deployments unattended. 'enabled' is required and must be given explicitly: turning unattended deployment on and turning it off are both deliberate acts, and neither is a safe default.

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

Input Schema

NameRequiredDescriptionDefault
enabledYestrue deploys builds observed on the tracked branch without asking; false leaves them built and waiting for an explicit deploy.
environmentNoScope the switch to one environment (its id, cluster name or role); absent, the switch is application-wide.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description goes beyond them by disclosing the consequence of enabling: builds observed on the tracked branch roll out to deployments unattended with no approval step. That is exactly the risk context an agent needs, though auth requirements and the effect on in-flight builds are unmentioned.

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?

Three tight sentences with the action front-loaded and the rationale trailing. The clause about 'enabled' being required slightly repeats the schema's required field, but it is short and adds the safety framing.

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 boolean toggle with full schema coverage and no output schema, the description supplies everything missing from the structured data: the observable effect of each value, the unattended-deploy consequence, and the deliberate-choice requirement.

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, including the environment scoping nuance, are already documented in structured fields. The description only reinforces that 'enabled' is required and must be explicit, which restates the schema's required list plus rationale; a baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Turn an Application's push-to-deploy switch on or off') plus the behavioral meaning of the switch, so the write counterpart to get_application_auto_deploy is obvious from the verb alone. It never explicitly contrasts itself with the sibling getter, which keeps it just short of a 5.

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?

Usage is implied rather than stated: the description explains what 'on' vs 'off' means and that the caller must choose deliberately, but gives no explicit when-to-use rule, no suggestion to read current state first via get_application_auto_deploy, and no prerequisites.

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.