create_spaceCreate a new Docmost space by providing a name, optional URL slug, and description to organize and manage pages and content.
Creates a new space.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the space. | |
| slug | No | Identifier for the URL. **Letters and numbers only** (no hyphens or underscores), e.g. 'mySpace'. | |
| description | No | Description (optional). |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. 'Creates a new space' only conveys the basic mutation; it says nothing about permissions, uniqueness, slug-generation behavior, or failure semantics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no filler. It front-loads the action and resource clearly, and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The input schema fully documents parameters and an output schema documents the return shape. However, important operational details remain unexplained, such as how slug handles null/default, whether names must be unique, and what permissions are required. For a simple create operation this is mostly adequate but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so name, slug, and description are fully documented in the input schema. The tool description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the exact operation ('Creates') and resource ('a new space'), which is unambiguous. Even with siblings like create_page and create_comment, the resource name 'space' clearly distinguishes this tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor does it state any exclusions or prerequisites. The agent must infer usage solely from the resource name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.