Skip to main content
Glama

init_project

Creates a new backend project directory with Express.js, TypeScript strict mode, and your choice of ORM. Optionally use a preset to generate a full domain with pre-built resources and JWT auth.

Instructions

Creates a new backend project directory with Express.js + TypeScript strict mode, ORM data layer (Prisma/Drizzle/Mongoose), Zod env validation, Swagger docs, Docker, ESLint, Vitest, and a .backgenrc.json manifest. Run add_plugin afterwards to add auth, payments, storage, rate-limiting, or CI/CD. Run generate_resource to add CRUD modules. Use --preset to generate a full domain (healthcare/saas/ecommerce/crm/lms) with pre-built resources and auto-installed JWT auth in one command. Call list_presets first to see what each domain preset includes. Typical generation takes 10–30 seconds with npm install being the longest step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name — used as the directory name and npm package name. Must start with a letter or number. Hyphens and underscores allowed. Examples: 'my-api', 'saas-backend', 'healthcare-api'.
ormNoDatabase ORM. prisma (PostgreSQL/MySQL/SQLite, recommended for relational), drizzle (lightweight SQL, closer-to-SQL control), mongoose (MongoDB, document-oriented). Defaults to prisma if not specified.prisma
presetNoDomain preset that generates multiple pre-wired resources in one command. Auto-installs JWT auth. Call list_presets first to see what each preset includes. Examples: 'saas-core' for multi-tenant orgs, 'healthcare' for patient/doctor/appointment.
defaultsNoUse default options (non-interactive). Recommended for AI use and automation. Set to false only if you want to prompt the user for each choice interactively.
skipInstallNoSkip npm install. Use true for CI pipelines, quick scaffolding demos, or when you want to install dependencies later manually. When true, remind the user to run 'npm install' before 'npm run dev'.
dirNoAbsolute or relative path to the parent directory where the project folder will be created. Defaults to the current working directory. Example: '/home/user/projects' or 'C:\Users\me\projects'.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses generation time (10–30 seconds), longest step (npm install), and mentions presets auto-installing JWT. Could be more explicit about overwrite behavior if directory exists, but otherwise transparent.

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?

Description is informative but slightly verbose; however, every sentence adds value. Well structured with clear flow: what it does, what to run next, special commands. Could be tightened without losing clarity.

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 the tool's complexity (6 parameters, no output schema), the description covers all necessary context: project contents, post-creation steps, preset usage, and typical duration. Complete enough for an agent to understand the tool's role in the workflow.

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 coverage is 100% with adequate descriptions for all 6 parameters. Description adds workflow context but does not significantly enhance parameter meaning beyond what schema already provides. Baseline score of 3 is appropriate.

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 explicitly states it creates a backend project with specific tools (Express.js, TypeScript, ORM, etc.), and distinguishes from sibling tools like add_plugin and generate_resource by naming them and their purposes.

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?

Clearly states when to use this tool (create a new project) and when to use siblings (add_plugin for auth/payments, generate_resource for CRUD). Advises calling list_presets first to see domain preset contents.

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/IbrahimKhaled19/BackGen'

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