Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Create Workspace

createWorkspace
Destructive

Create a new Cloady workspace with a name, slug, hue values, and optional icon URL to organize cloud application resources.

Instructions

Create a workspace (requires full scope)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "createWorkspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.18.0
    • removedInput schema / properties / requestBody / properties / paymentMethodId
      Removed value: -{
      -  "maxLength": 255,
      -  "pattern": "^pm_",
      -  "type": "string"
      -}
    • removedInput schema / properties / requestBody / properties / tier
      Removed value: -{
      -  "minLength": 1,
      -  "type": "string"
      -}
    • changedInput schema / properties / requestBody / required
      Previous value: -[
      -  "name",
      -  "slug",
      -  "hues",
      -  "tier"
      -]New value: +[
      +  "name",
      +  "slug",
      +  "hues"
      +]
  2. First observedv0.5.1

TDQS

B3.2/5.0
Behavior2/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 write/mutating nature is covered. The description's only added value is the authorization requirement ('requires full scope'), which is useful. It says nothing about slug uniqueness conflicts, whether the slug is immutable afterwards, or what happens on failure, which matters for a create operation with an open-world, destructive-flagged profile.

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?

One short sentence, front-loaded with the action and ending with the key constraint; there is zero filler. Its brevity is efficient but borders on under-specification given the nested body.

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?

Placeholder.

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 description coverage is 100%, including the nested requestBody required fields (name, slug, hues) and the slug pattern, so the schema carries nearly all parameter meaning. The description adds nothing beyond the schema, which is the expected baseline when coverage is complete.

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 states a specific verb+resource ('Create a workspace') that is immediately distinguishable from siblings like updateWorkspace, deleteWorkspace, and getWorkspace through the tool name. It does not, however, explicitly differentiate itself in prose from related helpers such as checkWorkspaceSlug or createWorkspaceInvitation.

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?

'Requires full scope' is a prerequisite, not a when-to-use rule. The description never says when to call this versus checking slug availability first (checkWorkspaceSlug), listing existing workspaces (listWorkspaces), or modifying one later (updateWorkspace), leaving the agent to infer the workflow.

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