Skip to main content
Glama

Create Project Workspace

create_project_workspace

Create an isolated project workspace with Git initialization, project-context bootstrap, and first milestone setup to start new projects with a structured workflow.

Instructions

Create a new isolated project workspace directory, initialize git, bootstrap the project context/brain, and set up first milestone.

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_project_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the project directory to create.
pathNoParent directory path (default is '.')..
templateNoWorkspace template name ('blank', 'nextjs', or 'python').blank

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose major side effects (directory creation, git init, context bootstrap, first milestone), but it does not say whether existing paths are overwritten, what permissions are required, whether failures leave partial state, or what happens when git is already initialized.

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?

The definition is a single front-loaded sentence that lists the key operations without filler. Every clause contributes to understanding the tool's scope.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the input schema is fully described. Still, for a multi-step workspace-creation mutation with no annotations, the description does not cover important prerequisites or the distinction from sibling scaffolding tools.

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 each of the three parameters is already documented with meaning and defaults. The description does not add extra parameter semantics such as template behavior, path resolution rules, or whether the workspace name must be unique. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Create') and resource ('new isolated project workspace directory') and lists the concrete setup steps it performs: git initialization, context/brain bootstrap, and first milestone. It is clear what the tool does, but it does not explicitly distinguish itself from close siblings such as bootstrap_project, create_directory, or adopt_existing_project.

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?

The description implies usage for starting a new isolated project workspace and packages several scaffolding actions together. However, it gives no explicit guidance on when to use this versus create_directory, bootstrap_project, or adopt_existing_project, and it does not state any exclusions or prerequisites.

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