Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Update Workspace

updateWorkspace
Destructive

Modify a Cloady workspace's name, slug, icon, colors, or paid plan settings; requires full-scope access.

Instructions

Update a workspace (requires full scope)

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

Input Schema

NameRequiredDescriptionDefault
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 / plan
      Added value: +{
      +  "const": "paid",
      +  "description": "Moves a free or trial workspace to the paid plan. Its apps are billed from then on, which needs a card, and it can have members. There's no way back to free or trial.",
      +  "type": "string"
      +}
  2. First observedv0.5.1

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is supplied. The description adds a useful auth requirement with "requires full scope," but it does not elaborate on destructive effects such as the irreversible plan change described only in the schema. With annotations carrying the main behavioral signal, a 3 is appropriate.

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?

The description is a single short sentence with the verb and resource front-loaded, and the permission note is attached cleanly. It contains no wasted wording, though its brevity borders on under-specification for a nested mutation tool.

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?

This is a destructive workspace mutation with a nested request body, six possible update fields, and no output schema. The description mentions only the scope requirement and omits what can be updated, the request-body semantics, and the irreversible plan-change behavior, leaving the agent without enough context to invoke it confidently.

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?

Schema description coverage is 50%, and the description adds no meaning for either top-level parameter. It does not mention that workspaceSlug is required, nor does it explain requestBody fields such as name, plan, slug, hues, iconUrl, or paymentMethodId, so it fails to compensate for the coverage gap.

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 phrase "Update a workspace" identifies the verb and resource, and "requires full scope" adds a permission condition. However, it does not specify which workspace attributes can be changed, so the purpose is clearer than a tautology but still vague about the operation's scope.

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?

The only contextual guidance is the permission prerequisite "requires full scope." There is no explicit guidance on when to use updateWorkspace instead of getWorkspace, createWorkspace, deleteWorkspace, or other workspace-related siblings, and no when-not-to-use cases are given.

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