Skip to main content
Glama

create_workspace

Create a new workspace in the caller's org. Works for both user and agent callers; agent-created workspaces attribute to the agent and enroll the agent's owning user as a co-owner so the human sees it in their dashboard. The new workspace is seeded with one primary surface matching mode: doc → a Notes surface (for prose), table → a Sheet surface (for records), html → a Mockup surface (sandboxed HTML preview). Decide the surface before you create: prose (briefs, notes, summaries, drafts) → doc; records with shared columns (tasks, leads, rows) → table; a deliverable that IS html (a page, mockup, dashboard, or visual meant to be seen or shared) → html, then write it with update_html — never to a local file, which the human can't see. If you omit mode, pass initial_markdown to signal a doc; with neither mode nor initial_markdown, an agent caller gets a guided error asking it to choose doc or table (so you never silently land on the wrong surface). An explicit mode is always honored. html is opt-in — never inferred for ambiguous content — so pass it explicitly when the deliverable is html (a mockup, page, or dashboard the user asked for), and only then. Add more surfaces of any kind later via create_surface. Agent-created workspaces default to org-visibility so sibling agents in the same org aren't 403'd. For prose content (briefs, summaries, changelogs) pass initial_markdown to seed the doc body in one call; the markdown is converted server-side, no need to hand-build ProseMirror JSON.

Input Schema

NameRequiredDescriptionDefault
modeNoKind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes surface: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet surface: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup surface (sandboxed HTML preview): opt in by passing it explicitly whenever the deliverable IS html — a landing-page mockup, a dashboard, a design preview, any page meant to be looked at — and write it with `update_html`; it is never inferred for ambiguous content. Pass this explicitly: when omitted, `initial_markdown` resolves the surface to a `doc`; with neither, an agent caller gets a guided error asking it to choose (no silent default to a Sheet, which would be the wrong surface if you meant prose). Add more surfaces of any kind via `create_surface` later.
nameYesThe workspace name. Required. Used to derive a slug if you don't pass one.
slugNoOptional URL-friendly slug (lowercase, kebab-case, 3-64 chars). Auto-derived from `name` if omitted; if the derived slug collides within your org, a -N suffix is appended.
initial_markdownNoOptional Markdown body to seed the workspace's doc surface on create. CommonMark + GFM (tables, task lists, strikethrough). When provided AND mode is omitted, mode defaults to 'doc'. Skips the empty default-column scaffolding too. Ignored when mode='html' (no markdown equivalent for HTML surfaces — use `update_html` after create). Use this for any prose-shaped output (briefs, summaries, status updates, changelog entries) instead of create + update_doc with hand-built JSON. `markdown` is accepted as an alias. The reply reports the stored doc body length, so check it is not 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / initial_markdown / description
      Previous value: -"Optional Markdown body to seed the workspace's doc surface on create. CommonMark + GFM (tables, task lists, strikethrough). When provided AND mode is omitted, mode defaults to 'doc'. Skips the empty default-column scaffolding too. Ignored when mode='html' (no markdown equivalent for HTML surfaces — use `update_html` after create). Use this for any prose-shaped output (briefs, summaries, status updates, changelog entries) instead of create + update_doc with hand-built JSON."New value: +"Optional Markdown body to seed the workspace's doc surface on create. CommonMark + GFM (tables, task lists, strikethrough). When provided AND mode is omitted, mode defaults to 'doc'. Skips the empty default-column scaffolding too. Ignored when mode='html' (no markdown equivalent for HTML surfaces — use `update_html` after create). Use this for any prose-shaped output (briefs, summaries, status updates, changelog entries) instead of create + update_doc with hand-built JSON. `markdown` is accepted as an alias. The reply reports the stored doc body length, so check it is not 0."
  2. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"Kind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes tab: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet tab: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup tab (sandboxed HTML preview): opt in by passing it explicitly whenever the deliverable IS html — a landing-page mockup, a dashboard, a design preview, any page meant to be looked at — and write it with `update_html`; it is never inferred for ambiguous content. Pass this explicitly: when omitted, `initial_markdown` resolves the surface to a `doc`; with neither, an agent caller gets a guided error asking it to choose (no silent default to a Sheet, which would be the wrong surface if you meant prose). Add more tabs of any kind via `create_surface` later."New value: +"Kind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes surface: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet surface: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup surface (sandboxed HTML preview): opt in by passing it explicitly whenever the deliverable IS html — a landing-page mockup, a dashboard, a design preview, any page meant to be looked at — and write it with `update_html`; it is never inferred for ambiguous content. Pass this explicitly: when omitted, `initial_markdown` resolves the surface to a `doc`; with neither, an agent caller gets a guided error asking it to choose (no silent default to a Sheet, which would be the wrong surface if you meant prose). Add more surfaces of any kind via `create_surface` later."
  3. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"Kind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes tab: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet tab: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup tab (sandboxed HTML preview, for landing-page mockups + design previews), opt-in only. Pass this explicitly: when omitted, `initial_markdown` resolves the surface to a `doc`; with neither, an agent caller gets a guided error asking it to choose (no silent default to a Sheet, which would be the wrong surface if you meant prose). Add more tabs of any kind via `create_surface` later."New value: +"Kind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes tab: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet tab: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup tab (sandboxed HTML preview): opt in by passing it explicitly whenever the deliverable IS html — a landing-page mockup, a dashboard, a design preview, any page meant to be looked at — and write it with `update_html`; it is never inferred for ambiguous content. Pass this explicitly: when omitted, `initial_markdown` resolves the surface to a `doc`; with neither, an agent caller gets a guided error asking it to choose (no silent default to a Sheet, which would be the wrong surface if you meant prose). Add more tabs of any kind via `create_surface` later."
  4. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"Kind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes tab: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet tab: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup tab (sandboxed HTML preview, for landing-page mockups + design previews), opt-in only. Pass this explicitly rather than relying on the fallback: when omitted it defaults to 'doc' if initial_markdown is supplied, otherwise 'table' — so a bare create with no content silently becomes a Sheet, which is the wrong surface if you meant to write prose. Add more tabs of any kind via `create_surface` later."New value: +"Kind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes tab: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet tab: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup tab (sandboxed HTML preview, for landing-page mockups + design previews), opt-in only. Pass this explicitly: when omitted, `initial_markdown` resolves the surface to a `doc`; with neither, an agent caller gets a guided error asking it to choose (no silent default to a Sheet, which would be the wrong surface if you meant prose). Add more tabs of any kind via `create_surface` later."
  5. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"Kind of the seeded primary surface. `table` mints a Sheet tab, `doc` mints a Notes tab, `html` mints a Mockup tab (sandboxed HTML preview, for landing-page mockups + design previews). Auto-defaults to 'doc' when initial_markdown is provided, 'table' otherwise; `html` is opt-in. Add more tabs of any kind via `create_surface` later."New value: +"Kind of the seeded primary surface — choose by what you're about to write. `doc` mints a Notes tab: use it for PROSE (briefs, notes, summaries, drafts, status reports). `table` mints a Sheet tab: use it for RECORDS (tasks, leads, rows, anything with shared columns). `html` mints a Mockup tab (sandboxed HTML preview, for landing-page mockups + design previews), opt-in only. Pass this explicitly rather than relying on the fallback: when omitted it defaults to 'doc' if initial_markdown is supplied, otherwise 'table' — so a bare create with no content silently becomes a Sheet, which is the wrong surface if you meant to write prose. Add more tabs of any kind via `create_surface` later."
  6. Changed3 schema fields changed
    • changedInput schema / properties / initial_markdown / description
      Previous value: -"Optional Markdown body to seed the workspace's doc surface on create. CommonMark + GFM (tables, task lists, strikethrough). When provided AND mode is omitted, mode defaults to 'doc'. Skips the empty default-column scaffolding too. Use this for any prose-shaped output (briefs, summaries, status updates, changelog entries) instead of create + update_doc with hand-built JSON."New value: +"Optional Markdown body to seed the workspace's doc surface on create. CommonMark + GFM (tables, task lists, strikethrough). When provided AND mode is omitted, mode defaults to 'doc'. Skips the empty default-column scaffolding too. Ignored when mode='html' (no markdown equivalent for HTML surfaces — use `update_html` after create). Use this for any prose-shaped output (briefs, summaries, status updates, changelog entries) instead of create + update_doc with hand-built JSON."
    • changedInput schema / properties / mode / description
      Previous value: -"Default-view preference for the first tab. Auto-defaults to 'doc' when initial_markdown is provided, 'table' otherwise. Picks the kind of the seeded primary surface; you can add more tabs of either kind via `create_surface` later. A workspace can hold any combination of doc and table surfaces, one or many of either."New value: +"Kind of the seeded primary surface. `table` mints a Sheet tab, `doc` mints a Notes tab, `html` mints a Mockup tab (sandboxed HTML preview, for landing-page mockups + design previews). Auto-defaults to 'doc' when initial_markdown is provided, 'table' otherwise; `html` is opt-in. Add more tabs of any kind via `create_surface` later."
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "table",
      -  "doc"
      -]New value: +[
      +  "table",
      +  "doc",
      +  "html"
      +]
  7. Changed2 schema fields changed
    • changedInput schema / properties / initial_markdown / description
      Previous value: -"Optional Markdown body to seed the workspace's doc surface on create. CommonMark + GFM (tables, task lists, strikethrough). When provided AND mode is omitted, mode defaults to 'doc'. Skips the empty default-column scaffolding too. Use this for any prose-shaped output — briefs, summaries, status updates, changelog entries — instead of create + update_doc with hand-built JSON."New value: +"Optional Markdown body to seed the workspace's doc surface on create. CommonMark + GFM (tables, task lists, strikethrough). When provided AND mode is omitted, mode defaults to 'doc'. Skips the empty default-column scaffolding too. Use this for any prose-shaped output (briefs, summaries, status updates, changelog entries) instead of create + update_doc with hand-built JSON."
    • changedInput schema / properties / mode / description
      Previous value: -"Default-view preference for the first tab. Auto-defaults to 'doc' when initial_markdown is provided, 'table' otherwise. Picks the kind of the seeded primary surface; you can add more tabs of either kind via `create_surface` later — a workspace can hold any combination of doc and table surfaces, one or many of either."New value: +"Default-view preference for the first tab. Auto-defaults to 'doc' when initial_markdown is provided, 'table' otherwise. Picks the kind of the seeded primary surface; you can add more tabs of either kind via `create_surface` later. A workspace can hold any combination of doc and table surfaces, one or many of either."
  8. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations the description carries the full burden and discharges it: agent-created workspaces attribute to the agent, enroll the owning user as co-owner, default to org-visibility to avoid 403s for sibling agents, and produce a guided error when neither mode nor initial_markdown is given. Return-format hints (stored doc body length) are also included.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, but the mode guidance is repeated almost verbatim from the schema description and padded across multiple sentences, inflating the definition well beyond what the structured fields don't already convey.

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?

For a mutation tool with no annotations and no output schema, the description covers actors, visibility defaults, seeding behavior, error handling, and downstream tool routing well. Minor gaps remain on things like permissions or how the created workspace id is returned, but the agent has enough to call it correctly.

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% and the schema already documents all four parameters in detail, so the baseline of 3 applies. The description largely restates the schema's mode and initial_markdown semantics rather than adding new syntax or constraints.

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 workspace in the caller's org') with the surface-seeding scope made explicit. An agent can distinguish it from create_surface and update_workspace 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 selection rules for doc/table/html based on the content you're about to write, names the alternative (create_surface) for adding surfaces later, and states when to pass initial_markdown vs. mode. The 'when not' for html (never inferred) is also spelled out.

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.