Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Update App

updateApp
Destructive

Modify an existing cloud app's name, status, source, scaling, or settings on Cloady to align its deployment with current needs.

Instructions

Update an app (name / status / version)

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>"
    },
    "name": "updateApp"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.18.0
    • removedInput schema / properties / requestBody / properties / autoDeploy
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedInput schema / properties / requestBody / properties / autoUpdate
      Added value: +{
      +  "description": "Git apps deploy every push to their branch, and template apps install new versions of their template",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / requestBody / properties / scale / properties / volumes / additionalProperties / maximum
      Previous value: -4096New value: +1024
    • addedInput schema / properties / requestBody / properties / source
      Added value: +{
      +  "description": "A git app's new source: changing its repoUrl, branch or subdir redeploys from it, from the repository's default branch when branch is left out. Other source types can't be changed.",
      +  "oneOf": [
      +    {
      +      "properties": {
      +        "autoUpdate": {
      +          "description": "Deploy every push to the branch: on unless set, except for development apps",
      +          "type": "boolean"
      +        },
      +        "branch": {
      +          "maxLength": 255,
      +          "type": "string"
      +        },
      +        "branchTracking": {
      +          "properties": {
      +            "mode": {
      +              "enum": [
      +                "off",
      +                "all",
      +                "match"
      +              ],
      +              "type": "string"
      +            },
      +            "pattern": {
      +              "maxLength": 255,
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "mode"
      +          ],
      +          "type": "object"
      +        },
      +        "profiles": {
      +          "items": {
      +            "pattern": "^[a-zA-Z0-9][a-zA-Z0-9_.-]+$",
      +            "type": "string"
      +          },
      +          "maxItems": 20,
      +          "type": "array"
      +        },
      +        "repoUrl": {
      +          "maxLength": 500,
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "subdir": {
      +          "maxLength": 255,
      +          "type": "string"
      +        },
      +        "type": {
      +          "const": "git",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "type",
      +        "repoUrl"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "properties": {
      +        "profiles": {
      +          "items": {
      +            "pattern": "^[a-zA-Z0-9][a-zA-Z0-9_.-]+$",
      +            "type": "string"
      +          },
      +          "maxItems": 20,
      +          "type": "array"
      +        },
      +        "subdir": {
      +          "maxLength": 255,
      +          "type": "string"
      +        },
      +        "type": {
      +          "const": "upload",
      +          "type": "string"
      +        },
      +        "uploadId": {
      +          "format": "uuid",
      +          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "type"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "properties": {
      +        "autoUpdate": {
      +          "description": "Install new versions of the template automatically: checked hourly, and an update that would change the app's price or type waits",
      +          "type": "boolean"
      +        },
      +        "name": {
      +          "maxLength": 80,
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "profiles": {
      +          "items": {
      +            "pattern": "^[a-zA-Z0-9][a-zA-Z0-9_.-]+$",
      +            "type": "string"
      +          },
      +          "maxItems": 20,
      +          "type": "array"
      +        },
      +        "type": {
      +          "const": "catalog",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "type",
      +        "name"
      +      ],
      +      "type": "object"
      +    }
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.5.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known from structured fields. The description adds nothing beyond that: it does not say whether this is a partial or whole-object replacement, that changing source.repoUrl/branch/subdir triggers a redeploy (only the schema's nested description says so), or that omitted fields are left untouched. For a destructive nested-object mutation this is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and front-loaded, but it is under-specified rather than concise. A single fragment cannot carry the semantic load of a five-parameter tool with a deeply nested oneOf request body, so brevity here costs the agent information instead of saving it.

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

Completeness2/5

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

Given a destructive, open-world mutation with a nested source oneOf and no output schema, the description leaves out the facts an agent most needs: partial-update semantics, redeploy side effects of changing source, and what happens to fields not supplied. The annotations cover safety but not these behavioral consequences.

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 description coverage is only about 20%, but this is misleading rather than merely silent: "version" is not a parameter at all, and the dominant requestBody sub-objects (scale, source, branch, tracking, autoUpdate, slug) go unmentioned. The two correct field names (name, status) are a partial match, so the description neither compensates for the coverage gap nor correctly summarizes the payload.

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

Purpose3/5

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

The description names a verb and resource ("Update an app"), which is enough to identify the operation. However, the parenthetical scope "(name / status / version)" is incomplete and partly wrong: the schema also accepts slug, scale, branch, source, tracking and autoUpdate, and has no "version" field. It also does nothing to distinguish this from sibling mutators such as updateWorkspace, updateVar, redeployApp or updateAppTracing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling to prefer. An agent asked to change an app's scale or redeploy from a new branch has no textual basis for choosing updateApp over redeployApp or createAppDeploy; only the parameter names hint at it.

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