Skip to main content
Glama
fhyxz1

Builder-Proj-MCP Server

by fhyxz1

build_project

Create a new project with any supported framework such as Spring Boot, React, Vue, Next.js, FastAPI, and others. Configure options including TypeScript, testing, Docker, and database.

Instructions

Build a new project with specified framework. Supported frameworks: spring-boot, spring, spring-mvc, spring-webflux, react, react-vite, react-cra, vue, vue3, vue-vite, fastapi, fastapi-uvicorn, fastapi-gunicorn, django, django-rest, django-cms, flask, flask-rest, flask-sqlalchemy, vite, vite-vanilla, vite-ts, express, express-ts, express-rest, fastify, fastify-ts, fastify-rest, nestjs, nest, nestjs-rest, nestjs-graphql, next, nextjs, next-app, next-pages, nuxt, nuxt3

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameYesName of the project to create
projectTypeNoType of project (e.g., web, api, mobile)
frameworkYesFramework to use. Options: spring-boot, spring, spring-mvc, spring-webflux, react, react-vite, react-cra, vue, vue3, vue-vite, fastapi, fastapi-uvicorn, fastapi-gunicorn, django, django-rest, django-cms, flask, flask-rest, flask-sqlalchemy, vite, vite-vanilla, vite-ts, express, express-ts, express-rest, fastify, fastify-ts, fastify-rest, nestjs, nest, nestjs-rest, nestjs-graphql, next, nextjs, next-app, next-pages, nuxt, nuxt3
optionsNoAdditional options for the project builder
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose creation side effects (overwriting, directory creation), permission requirements, or resource impact. Only the action 'build' is stated.

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 sentence followed by a list. It is front-loaded with the purpose and concise with no extraneous information.

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?

Given the tool's complexity (4 parameters, nested options, many frameworks), the description is insufficient. It does not explain return values, behavior on failure, or what 'building' entails (e.g., scaffolding).

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 parameters. The description repeats the framework list but adds no extra meaning. 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 clearly states the tool builds a new project with a specified framework. The verb 'build' and resource 'project' are explicit. However, it does not differentiate from sibling tool 'list_frameworks', which simply lists frameworks.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or limitations. The description merely states what it does without context for when it is appropriate.

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/fhyxz1/builder-proj-mcp'

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