Skip to main content
Glama

workspace_create

Create a new team workspace owned by the calling user. Returns its id and slug — pass either to workspace.switch to start working inside it. slug is derived from name when omitted. NOT idempotent: calling twice with the same name yields two workspaces (the second gets a -1 slug suffix), so check workspace.list first if the workspace may already exist.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWorkspace display name, e.g. 'TUI BLUE'.
slugNoURL-friendly slug: lowercase letters, digits and single dashes between them (e.g. 'tui-blue'), max 100 chars. Omit to derive one from `name` (lowercased, spaces to dashes, uniqueness suffix added when taken). An explicit slug is NOT auto-uniquified — a collision is an error.
descriptionNoOptional workspace description.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare idempotentHint=false and destructiveHint=false, but the description adds the observable consequence: two calls with the same name produce two workspaces, the second with a '-1' slug suffix, and an explicit slug collision is an error rather than being uniquified. It also discloses the return payload (id, slug). The only gap is that permission or ownership requirements are only gestured at, not specified.

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 sentences, front-loaded with the operation and return value, then the non-idempotency warning. Every sentence carries distinct information with no filler.

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?

For a four-parameter creation tool with no output schema, the definition covers the return value, the derivation rule for the optional slug, the duplicate-creation hazard, and the correct next step. Nothing an agent needs to invoke it safely is missing.

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 coverage is 100% and the schema already documents name, slug derivation, description, and in_workspace in detail. The description's note that 'slug is derived from name when omitted' largely restates the schema, so it does not add much meaning beyond the structured fields.

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 and resource ('Create a new team workspace') plus ownership semantics ('owned by the calling user'), which cleanly separates it from sibling read tools like workspace_list and workspace_current. An agent can identify the operation without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing: check workspace.list first if the workspace may already exist, and pass the returned id or slug to workspace.switch to begin working. It also names the concrete failure mode of blind retry, so the agent knows what not to do.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.