Skip to main content
Glama

Coline

Create a workspace

create_workspace

Creates a team workspace the person owns: tasks, docs, notes, sheets, mail, calendar and messages for a team or project. It starts a free 14-day trial with no card; if the person already used their trial, the result has a checkout link they open to pay. Use it when the person asks for a new workspace, or has only their personal one and wants to work with a team. Pass the returned slug as workspace to every other action.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
trialNoStart the free trial (no card). False opens checkout.
planKeyNoAlways the Team plan; the retired values workspace and workspace_ai also start Team.team
seatCountNoSeats to start with; a trial grows seats as people join.
billingIntervalNomonth

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
slugYes
statusYes
checkoutUrlYes
trialEndsAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the commercially important behavior: a free 14-day trial with no card, and a checkout-link fallback when the trial was already consumed. It also explains the ownership outcome and the post-call contract (reuse the returned slug as `workspace`), which is exactly the context an agent needs before invoking a billing-adjacent creation.

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 sentences, each doing distinct work: what is created, what the trial/checkout outcome is, and when plus how to follow up. The most actionable item (slug usage) is saved for the end only because it depends on the preceding context, and no sentence is redundant.

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

Completeness4/5

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

An output schema exists, so return-value detail is optional, yet the description still surfaces the one return field that matters downstream (the slug). For a non-idempotent creator with billing implications, the main remaining gap is silence on duplicate-name behavior and any permission or plan prerequisites.

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 60%, and the schema already documents trial, planKey, seatCount and billingInterval including defaults, ranges and the deprecated enum values. The description only indirectly touches the `trial` parameter through the trial/checkout narrative and adds nothing about name uniqueness or seat/billing choices, so it neither compensates for the uncovered fields nor clarifies the enum edge cases.

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?

"Creates a team workspace the person owns" gives a specific verb plus resource, and the enumeration of contained surfaces (tasks, docs, notes, sheets, mail, calendar, messages) makes clear what a workspace is. It implicitly separates itself from update_workspace but never distinguishes itself from top-level creators like create_team or create_project, which sit in the same catalog.

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

Usage Guidelines4/5

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

It gives concrete triggering conditions: the person asks for a new workspace, or has only a personal one and wants team collaboration. It also routes the caller onward, instructing that the returned slug be passed as `workspace` to every other action. There is no explicit when-not or negative alternative (e.g., joining an existing team instead).

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