OpenUptime

create_workspace

Create a new workspace owned by the signed-in user and initialize its first project. Use it to set up a fresh workspace; requires OAuth access for all workspaces, not a workspace-scoped API key.

Instructions

Create a workspace owned by the signed-in user, including its first project. Use create_project instead to organize an existing workspace. Requires an OAuth grant for all workspaces; a workspace-scoped API key cannot create one. Returns the new workspace record and id; use list_workspaces to discover its project.

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

Input Schema

Name	Required	Description
`name`	Yes	Display name for the new workspace or project; not an existing resource id.
`project`	No	Project id (from list_workspaces). Omit to use the default project of the workspace.
`workspace`	No	Workspace id (from list_workspaces). Omit to use the default one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Oct 23, 2026
- addedInput schema / properties / name / description
```
Added value: +"Display name for the new workspace or project; not an existing resource id."
```
First observedv0.1.0Oct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds genuinely non-schema context: the auth/grant requirement and what is returned ('the new workspace record and id'). Minor confusion remains around 'including its first project' versus the project parameter's 'omit to use the default project', which reads ambiguously for a creation tool.

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?

Three short sentences, with the core action front-loaded and the alternative, prerequisite, and return value following in priority order. No filler.

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?

No output schema exists, and the description compensates by stating the return shape; the auth prerequisite is also covered. The only residual gap is the unclear relationship between 'including its first project' and the optional project/workspace parameters.

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%, so all three parameters are already documented in structured form; the description adds no syntax or meaning beyond pointing at list_workspaces for ids. Baseline 3 applies when the schema does the heavy lifting.

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 plus ownership scope: 'Create a workspace owned by the signed-in user, including its first project.' It explicitly contrasts with the nearest sibling, create_project, so an agent can distinguish the two without opening either 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?

Names the alternative tool and the condition that selects it ('Use create_project instead to organize an existing workspace'), and adds a hard prerequisite ('Requires an OAuth grant for all workspaces; a workspace-scoped API key cannot create one'). Both when-to-use and when-not-to-use are stated.

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