Planning System MCP Server

create_workspace

Create a new workspace in an organization. The slug is auto-generated from the title and de-duplicated within the org.

Instructions

Create a new workspace inside an organization. Returns the new workspace row. The slug is auto-generated from the title and de-duplicated within the org.

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": {
      "organization_id": "<organization_id>",
      "title": "<title>"
    },
    "name": "create_workspace"
  }
}

Input Schema

Name	Required	Description
`organization_id`	Yes
`title`	Yes
`description`	No
`icon`	No	Optional emoji or icon token.
`slug`	No	Optional. Auto-generated from title if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.0Jun 18, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses slug auto-generation and deduplication, which is helpful, but does not disclose other behavioral traits like authorization requirements, idempotency, or side effects beyond 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?

Two short, front-loaded sentences with no waste. First sentence states action and return; second adds crucial detail about slug behavior.

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 creation tool with no output schema, it covers key aspects: what is created, what is returned, and a notable behavior. Lacks detail on optional parameters and error conditions, but sufficient for typical use.

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 40% (only icon and slug have schema descriptions). The description adds value by explaining slug auto-generation, but does not clarify the meaning of organization_id or title beyond what is obvious from context. Required parameters lack elaboration.

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 it creates a new workspace inside an organization and returns the row. The verb 'create' and resource 'workspace' are specific and distinguish from sibling tools like list_workspaces or update_goal.

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

Usage Guidelines3/5

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

Implies usage when you want to create a workspace in an organization, but provides no guidance on when to use alternatives or prerequisites. No mention of when not to use this tool.

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