Skip to main content
Glama

dart-create

Create new Dart projects from templates like console, package, server-shelf, or web applications. Specify project name, output directory, and additional options to generate project structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateNoTemplate to use for project generationpackage
projectNameYesName of the project to create
outputNoDirectory where to create the project
optionsNoAdditional project creation options

Implementation Reference

  • The main handler function for the 'dart-create' tool. It constructs arguments for the 'dart create' command using the provided template, project name, output directory, and additional options, then executes it via executeDartCommand and returns the result.
    export async function create(args: z.infer<typeof createSchema>) {
      const { template, projectName, output, options = [] } = args;
      
      // If output is provided, use it as the target directory
      // Otherwise, use projectName as both the target directory and the package name
      const targetDir = output || projectName;
      
      // Convert relative path to absolute path
      const absoluteTargetDir = toAbsolutePath(targetDir);
      
      // When output and projectName are both provided, we might want to use
      // projectName to name the package but create it in the output directory.
      // However, the Dart CLI doesn't have a separate flag for this.
      // The project name will be derived from the directory name.
      
      const cmdArgs = [
        '-t', template,
        ...options,
        // Use the target directory as the positional argument
        absoluteTargetDir
      ];
      
      console.log(`Creating Dart project with template '${template}' in directory: ${absoluteTargetDir}`);
      const { stdout, stderr } = await executeDartCommand('create', cmdArgs);
      
      return {
        content: [
          { type: "text" as const, text: stdout || stderr }
        ],
        isError: !!stderr
      };
    }
  • Zod schema defining the input parameters for the 'dart-create' tool: template (enum with default), projectName (string), output (optional string), options (optional array of strings).
    export const createSchema = z.object({
      template: z.enum(['console', 'package', 'server-shelf', 'web']).default('package')
        .describe('Template to use for project generation'),
      projectName: z.string().describe('Name of the project to create'),
      output: z.string().optional().describe('Directory where to create the project'),
      options: z.array(z.string()).optional().describe('Additional project creation options')
    });
  • src/index.ts:35-35 (registration)
    Registration of the 'dart-create' tool on the MCP server, associating the name, input schema shape, and handler function.
    server.tool('dart-create', createSchema.shape, create);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/egyleader/dart-mcp'

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