Skip to main content
Glama
vertracloud

@vertracloud/mcp

Official
by vertracloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_app_config

DestructiveIdempotent

Changes the application's configuration: name, memory, main file, runtime version, start command, build command and deploy behavior (zero_downtime, auto_rollback, health_check_path).

Instructions

Changes the application's configuration: name, memory, main file, runtime version, start command, build command and deploy behavior (zero_downtime, auto_rollback, health_check_path). Zero downtime "on" and auto rollback depend on the plan (PLAN_DOES_NOT_SUPPORT_ZERO_DOWNTIME / PLAN_DOES_NOT_SUPPORT_AUTO_ROLLBACK). (scope: apps:write)

Input Schema

NameRequiredDescriptionDefault
idYesApplication ID
mainNo
nameNo
buildNoBuild command; empty string removes it
startNo
memoryNo
versionNo
descriptionNo
workspace_idNo
auto_rollbackNoAutomatically roll back a deploy that fails to start
zero_downtimeNoDeploy without downtime: auto, on or off
health_check_pathNoHealth check path: starts with /, printable ASCII without spaces, up to 200 characters; null clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / id / minLength
      Added value: +1
  2. Changed4 schema fields changedv0.2.1
    • addedInput schema / properties / auto_rollback
      Added value: +{
+  "description": "Automatically roll back a deploy that fails to start",
+  "type": "boolean"
+}
    • addedInput schema / properties / build
      Added value: +{
+  "description": "Build command; empty string removes it",
+  "type": "string"
+}
    • addedInput schema / properties / health_check_path
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "pattern": "^\\/[\\x21-\\x7e]*$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Health check path: starts with /, printable ASCII without spaces, up to 200 characters; null clears it"
+}
    • addedInput schema / properties / zero_downtime
      Added value: +{
+  "description": "Deploy without downtime: auto, on or off",
+  "enum": [
+    "auto",
+    "on",
+    "off"
+  ],
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and openWorld=true, so the safety profile is covered. The description adds genuinely new behavior: the required `apps:write` scope and the exact plan-gated failure codes (PLAN_DOES_NOT_SUPPORT_ZERO_DOWNTIME / _AUTO_ROLLBACK), which tell the agent in advance which field combinations can fail. It does not say whether omitted fields are preserved or overwritten.

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 tight segments — what changes, which plan constraints can bite, and the required scope — with the enumeration front-loaded. Nothing is repeated from the schema or annotations, and the error-code names save a round trip.

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 12-parameter destructive mutation with no output schema, the description covers field scope, auth scope and known failure modes, which is most of what an agent needs. The remaining gap is update semantics for fields not supplied (partial patch vs. replace) and any confirmation of what is returned.

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

Parameters4/5

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

Schema coverage is only 42%, so the description must compensate, and it does: it names 10 of the 12 parameters in plain terms (main file, runtime version, start/build command, zero_downtime, auto_rollback, health_check_path). Only `description` and `workspace_id` go unmentioned, and it adds no unit/format detail beyond the names.

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 ('Changes') and resource ('application's configuration'), then enumerates the exact fields covered including app-specific ones like runtime version, start/build command and deploy behavior. This clearly separates it from siblings such as update_database, update_workspace, or update_profile.

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 by the enumerated fields and the plan-dependent caveat, but there is no explicit routing guidance (e.g., use create_app to make a new app, start_app/stop_app for lifecycle, deploy_app to ship a build). An agent can infer this is the mutation for existing app config, but exclusions are absent.

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

Deploy Server

Other Tools