jotbus

create_workspace

Creates and connects a new Jotbus workspace on this machine for shared encrypted notes and files—persistent when signed in, otherwise temporary for 60 minutes. Returns its name and sharing method.

Instructions

Create a new Jotbus workspace and connect it on this machine. Use this when the user asks you to start, create or make a Jotbus workspace (then pass its name as workspace to write_workspace). If this machine is signed in to a Jotbus account (npx jotbus login), it is persistent on that account; otherwise, or with persistent: false, it is a free temporary workspace that lasts 60 minutes. Returns its name and how to share it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_workspace"
  }
}

Input Schema

Name	Required	Description
`name`	No	Optional name (lowercase letters, digits, ".", "_", "-"). Persistent workspaces only; random otherwise.
`persistent`	No	Default: true when this machine is signed in, false otherwise. Persistent workspaces need `npx jotbus login` and a subscription.
`description`	No	Optional description (persistent workspaces).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.0Nov 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the persistence fork (account-backed vs 60-minute temporary), the login/subscription prerequisite, and the return shape (name plus sharing instructions). It omits failure modes such as name collisions or invalid characters, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded on purpose then usage then behavior, with no filler. The parentheticals are dense but each carries actionable information; slightly packed rather than wasteful.

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 simple 3-optional-parameter creation tool with no output schema, the description covers persistence, prerequisites, and return content adequately. Only error/precondition edge cases are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine cross-tool semantics: the created name is meant to be passed as `workspace` to write_workspace, and it clarifies that `persistent: false` yields a temporary workspace. That meaning is not derivable from the schema alone.

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?

Description opens with a specific verb+resource: "Create a new Jotbus workspace and connect it on this machine." It also names the sibling follow-up (write_workspace) and implicitly contrasts with list_workspaces, so an agent can distinguish create from enumerate without opening a schema.

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

Usage Guidelines4/5

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

Explicit trigger phrase: "Use this when the user asks you to start, create or make a Jotbus workspace," plus a concrete next step (pass the name to write_workspace). It does not explicitly say when NOT to use it or point at list_workspaces as the alternative, so it stops short of a 5.

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

Deploy Server