Skip to main content
Glama
stefanoamorelli

ember-cli-mcp

ember_new

Create a new Ember application by generating a directory and running ember init with customizable options.

Instructions

Creates a new directory and runs ember init in it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_nameYesName of the new application
dry_runNoShow what would be created without actually creating it
verboseNoShow verbose output
blueprintNoBlueprint to use for generating the applicationapp
skip_npmNoSkip npm/yarn install
skip_gitNoSkip git initialization
welcomeNoInstall and use ember-welcome-page
package_managerNoPackage manager to use
directoryNoDirectory to create the app in
langNoSet the base language of the application
lint_fixNoAutomatically fix linting errors
embroiderNoUse Embroider build system
ci_providerNoCI provider to set up
ember_dataNoInclude ember-data
interactiveNoCreate app interactively
typescriptNoSet up TypeScript
strictNoUse GJS/GTS templates by default
cwdNoWorking directory to run the command in
Behavior2/5

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

With no annotations, the description should fully disclose behavioral traits. It mentions creation and initialization but omits details like directory existence handling, network use, or side effects.

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?

The description is a single concise sentence with no unnecessary words. However, it lacks structure or front-loading of key information.

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

Completeness1/5

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

With 18 parameters and no output schema, the description is severely lacking. It does not explain parameter behavior, workflow, or return values.

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%, so baseline is 3. The description adds no parameter-specific meaning beyond the schema.

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 it creates a new directory and runs ember init. However, it does not distinguish itself from the sibling 'ember_init' which may have overlapping functionality.

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 vs alternatives like ember_init. No context on prerequisites or typical scenarios.

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/stefanoamorelli/ember-cli-mcp'

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