Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Transfer App

transferApp
Destructive

Move an app from one Cloady workspace to another by providing the source and target workspace slugs.

Instructions

Transfer an app to another workspace

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": "transferApp"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.0
    • addedInput schema / properties / requestBody / properties / region
      Added value: +{
      +  "maxLength": 40,
      +  "minLength": 1,
      +  "type": "string"
      +}
  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 flag destructiveHint=true and openWorldHint=true, so the description's burden is to explain what the destruction means — does the app leave the source workspace, are deploys/domains/env vars carried over, is it reversible? None of this is stated. The description adds no behavioral context beyond what the annotations and schema already convey, though it does not contradict them.

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

Conciseness3/5

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

A single short sentence with no filler and the destination front-loaded, which is structurally sound. However, its brevity comes at the cost of substance for a destructive multi-parameter operation, so it is terse rather than genuinely efficient.

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?

For a destructive mutation with a nested request body, low schema coverage, and no output schema, the definition is far too thin. It leaves the agent unaware of permission requirements, side effects on the source workspace, and how the flat env/region parameters interact with the nested body.

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

Parameters2/5

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

With 5 parameters and only 20% schema description coverage, the description should clarify the meaning of env, region, workspaceSlug, and appSlug, and especially that targetWorkspaceSlug lives inside requestBody. It only vaguely gestures at the target workspace and says nothing about which workspace env/region apply to.

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?

The description gives a specific verb and resource ('Transfer an app') plus a destination ('to another workspace'), which is clearer than the bare tool name. It does not differentiate from any sibling, though none of the listed siblings (e.g. transferWorkspaceOwnership, updateApp) obviously overlaps, so the risk of confusion is low.

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 guidance on when to use this tool, what prerequisites are required (membership or admin rights in both the source and target workspaces), or what alternative to use if the target workspace differs. The agent must infer everything from the single sentence.

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