Skip to main content
Glama
gwmage

Rootr MCP Server

Create a brand-new Rootr workspace from a scaffold tree

rootr_create_workspace

Create a new Rootr workspace with a pre-populated document tree including databases, spreadsheets, forms, and issue trackers based on a scaffold plan and user answers.

Instructions

Create an entirely new Rootr (루터) workspace pre-populated with the given document tree. REQUIRES an account key (PAT) with the workspaces:create scope — a workspace-scoped key cannot do this. PRECONDITION: call rootr_scaffold_plan first and ask the user its 3-10 clarifying questions; design the tree from their answers. Build a real tool, not a pile of thin markdown files: mix DATABASE (board/timeline views, seed rows), SPREADSHEET (formulas), FORM, ISSUE_TRACKER and rich multi-section DOCUMENTs where they fit, and set an emoji icon on folders/databases/key documents. The tree shape follows the scaffold schema in llms.txt (max 200 nodes). AFTER creating: if your runtime can receive HTTP callbacks, offer the user to register a webhook on the new tree (rootr_create_webhook with scopeNodeId) so changes flow back to you — skip your own actorId to avoid self-triggering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new workspace
treeYesScaffold tree — an ARRAY of node objects to populate the new workspace with (see llms.txt tree schema)
intentNoOriginal natural-language intent, for reference/regeneration
Behavior5/5

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

Discloses authorization requirements, tree size limit, and after-creation behavior, adding significant context beyond the annotations which only indicate non-read-only and non-destructive.

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?

The description is lengthy but each sentence adds valuable context; front-loaded with core action and critical instructions, making it effective for agent use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensively covers prerequisites, tree design guidance, and next steps, making it complete for a complex creation tool with no output schema.

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 covers all parameters; description enriches by explaining the tree structure expectations and the purpose of the intent parameter, adding value beyond the schema.

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?

The description clearly states the tool creates a new Rootr workspace from a scaffold tree, distinguishing it from other creation tools like rootr_create_presentation.

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?

Explicitly mentions required scope, precondition to call rootr_scaffold_plan first, and post-creation suggestion for webhook, guiding appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gwmage/rootr-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server