Skip to main content
Glama
starter-series

create-starter

by starter-series
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_project

Scaffold a new project from a Starter Series template and optionally initialize a git repo. Start from templates for MCP servers, npm packages, extensions, or Docker deploys.

Instructions

Scaffold a new project from a Starter Series template

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name (alphanumeric start, '-' or '_' only)
init_gitNoInitialize a fresh git repo after scaffold (default: true)
templateYesTemplate ID (use list_templates to see options)
output_dirNoOutput directory (defaults to ./<name>, relative to the MCP server's cwd)
descriptionNoOne-line project description

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
filesReplacedYes
filesExtractedYes
gitInitializedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.3
    • changedInput schema / properties / template / enum
      Previous value: -[
-  "mcp-server",
-  "mcp-server-python",
-  "npm-package",
-  "discord-bot",
-  "telegram-bot",
-  "browser-extension",
-  "vscode-extension",
-  "electron-app",
-  "react-native",
-  "cloudflare-pages",
-  "docker-deploy"
-]New value: +[
+  "mcp-server",
+  "mcp-server-python",
+  "npm-package",
+  "browser-extension",
+  "vscode-extension",
+  "docker-deploy"
+]
  2. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It only implies file creation via 'Scaffold' and omits side effects such as git initialization (default true), output directory behavior, overwrite handling, and required permissions.

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 description is a single front-loaded sentence with no wasted words. It is appropriately concise for a tool whose parameter details are fully covered by the schema.

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

Completeness2/5

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

For a 5-parameter creation tool with no annotations, the description is incomplete. Although output schema and parameter descriptions are rich, the description omits usage guidance, side effects, and behavioral context needed to invoke the tool safely and correctly.

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 the schema already documents all five parameters thoroughly. The description adds no additional parameter meaning beyond what the schema provides, making the baseline score of 3 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 states a specific verb ('Scaffold') and resource ('new project') with a clear source ('Starter Series template'). It distinguishes the tool from sibling audits and add_component by being project-level, but it does not explicitly name alternatives like list_templates or add_component.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance is provided. The phrase 'from a Starter Series template' hints at a prerequisite, but the description never mentions list_templates or explains selection relative to siblings.

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

Deploy Server

Other Tools