Skip to main content
Glama
Dqrshan

Zip Hive Scaffold

by Dqrshan

Create Custom Project

scaffold_create_project
Idempotent

Generate a project folder with specified files and subdirectories from a JSON definition, supporting overwrite control.

Instructions

Create a project from a custom structure definition. Pass files and optional folders as JSON.

Args:

  • project_name (string): Name of the project folder

  • root_dir (string): Parent directory where the project folder will be created

  • files (array): Array of { path: string, content?: string } objects

  • folders (array, optional): Array of folder paths to create (empty dirs)

  • overwrite (boolean): Whether to overwrite existing files (default: false)

Returns: A summary of created, skipped, and errored files/folders.

Example: scaffold_create_project( project_name="my-api", root_dir="/home/user/projects", files=[ {"path": "src/index.ts", "content": "console.log('hello')"}, {"path": "package.json", "content": "{ "name": "my-api" }"} ], folders=["src/routes", "src/models"] )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesArray of files to create
foldersNoArray of folder paths to create (empty directories)
root_dirYesAbsolute path to the parent directory
overwriteNoWhether to overwrite existing files
project_nameYesName of the project folder to create
Behavior4/5

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

The description discloses the return value ('summary of created, skipped, and errored files/folders') and parameter defaults (overwrite default false). These behaviors align with the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) and add context beyond what annotations alone provide.

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 well-organized with Args, Returns, and Example sections. It is thorough yet every sentence contributes meaningful information—no filler. The example is compact and illustrates the exact structure expected.

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?

Given that there is no output schema, the description specifies the return structure. It covers all parameters, their types, optionality, defaults, and an example. The tool's behavior and parameters are fully described, making it complete for an agent to use correctly.

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?

The input schema has 100% description coverage, so the baseline is 3. The description enhances this by providing a structured overview of each parameter and a concrete example showing the expected shape of the files array, which adds practical 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 a specific verb and resource: 'Create a project from a custom structure definition.' This distinguishes it from sibling tools like scaffold_list_templates, scaffold_from_template, scaffold_create_folders, and scaffold_create_files, which have different scopes.

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?

The description specifies it is for custom structure definitions, which implies it is used when creating a project from scratch rather than from a predefined template. However, it does not explicitly mention alternatives or provide exclusionary guidance, so it falls 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.

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/Dqrshan/ziphive-scaffold'

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