Skip to main content
Glama

Create space

create_space

Start a new top-level container for wiki pages. Optionally assign it to an organization and use an idempotency key to prevent duplicate spaces.

Instructions

Create a space; the caller becomes its owner (write scope). slug is derived from name when omitted. Use to start a new top-level container of pages; to add a page inside an existing space use create_page, and to rename a space use update_space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesspace name (1-200 chars)
slugNooptional url slug; derived from name when omitted
org_idNooptional org id to own the space (caller must be a member); omit for a personal space
idempotency_keyNooptional client-generated key; a retry with the same key returns the original result instead of creating a duplicate space (safe retries after a dropped connection)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses ownership effect ('caller becomes its owner') and slug derivation behavior. Annotations already indicate mutation; description adds relevant context without contradiction.

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 sentences, front-loaded with action and key outcome, no unnecessary words.

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?

Given output schema exists and schema coverage is complete, the description effectively covers purpose, usage, and behavioral traits, making it fully informative for an AI agent.

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%, so schema already documents parameters. Description adds no extra parameter details beyond mentioning slug derivation, which is already in schema.

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?

Clearly states action ('Create a space') and resource. Distinguishes from siblings by mentioning create_page and update_space as alternatives.

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?

Explicitly says when to use (start new top-level container) and when not to (use create_page for pages, update_space for renaming). Also explains slug derivation.

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