create_spaceCreate a Docmost wiki space with a name, slug, and optional description; the creator becomes its admin, and workspace admin or owner permission is required.
Create a space; you become its admin. Needs a Docmost workspace admin or owner.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Space name. | |
| slug | Yes | Short name used in URLs: letters and digits only. | |
| description | No | Short description. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already state this is a non-read-only, non-destructive, closed-world operation. The description adds two things annotations cannot: the privilege requirement and the resulting admin membership. Nothing contradicts the annotations.
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?
Two compact clauses with zero filler; the effect and the precondition are both front-loaded. 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?
With a full output schema, complete parameter docs, and clear safety annotations, the description covers the remaining gaps: authorization and the caller's resulting role. Only minor detail like uniqueness of slug is left to inference.
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?
All three parameters are fully documented in the schema, including slug format constraints and defaults. The description adds no parameter detail, which is acceptable given 100% schema coverage but earns only the baseline.
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?
Specific verb 'Create' plus resource 'space', and it discloses the immediate side effect that the caller becomes admin. It does not explicitly contrast with update_space or list_spaces, but the create-vs-update distinction is unambiguous.
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?
Gives the concrete precondition that the caller must be a Docmost workspace admin or owner, which is the main gate on use. It does not spell out when to prefer other tools, but no real alternative exists for creating a space.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.