Skip to main content
Glama

Create a shared workspace

create_workspace
Idempotent

Creates an empty workspace owned by the connected account. Hosting projects in that workspace requires its own active subscription.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, non-open-world write, so the safety profile is covered. The description adds value beyond that: the created workspace is empty, ownership binds to the connected account, and project hosting depends on a separate subscription. It does not say whether the call is billable or what happens on a duplicate name.

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?

Two short sentences, the core action front-loaded, and the subscription caveat placed after it. Nothing is padded or repeated from the title.

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

Completeness3/5

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

There is no output schema, yet the description never indicates what a successful creation returns, which matters because follow-up calls (invite_workspace_member, create_project) presumably need the new workspace identifier. For a two-parameter, no-annotation-gap mutation tool this is adequate but leaves a practical hole.

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?

With 50% schema description coverage, only 'name' is undocumented; the schema fully explains idempotency_key and its reuse-on-uncertain-response pattern. The description mentions neither parameter, so it neither compensates for the bare 'name' field (length limits, uniqueness, naming rules) nor reinforces the idempotency contract.

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?

States a specific verb and resource ('Creates an empty workspace') plus ownership scope ('owned by the connected account'), which is more than a restatement of the title. It does not distinguish itself from the create_project / create_dynamic_project siblings, so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it creates a container before other resources exist. The second sentence adds a genuine prerequisite (hosting projects requires a separate active subscription), but there is no explicit when-to-use versus create_project or accept_workspace_invitation, and no stated failure conditions.

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.

Resources