Skip to main content
Glama

create_project

Create a new project with a name and optional description to organize your deployments and resources in Coolify.

Instructions

Create a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
descriptionNoProject description

Implementation Reference

  • Handler case for 'create_project': validates the 'name' parameter is required, then POSTs to the /projects endpoint via the CoolifyClient.
    case 'create_project':
      requireParam(args, 'name');
      return client.post('/projects', args);
  • TypeScript interface CreateProjectInput defining the input schema: name (required string) and description (optional string).
    export interface CreateProjectInput {
      name: string;
      description?: string;
    }
  • Tool definition registration for 'create_project' with name, description, and inputSchema specifying name (required) and description (optional).
    {
      name: 'create_project',
      description: 'Create a new project',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Project name' },
          description: { type: 'string', description: 'Project description' }
        },
        required: ['name']
      }
    },
  • Helper function requireParam used by the handler to validate that required parameters like 'name' are present in the args.
    function requireParam(args: ToolArgs, param: string): void {
      if (!args[param]) {
        throw new McpError(ErrorCode.InvalidParams, `${param} is required`);
      }
    }
Behavior1/5

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

With no annotations, the description must fully disclose behavior, but it only states the action without mentioning side effects, idempotency, or success/error outcomes.

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

Conciseness3/5

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

The description is a single short sentence, which is concise but lacks necessary detail; it earns its place but could be more informative without being lengthy.

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?

The tool is simple with 2 parameters, but the description does not explain return values, error conditions, or the scope (e.g., current team), leaving gaps for an AI agent.

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 both parameters. The description adds no additional meaning beyond what the schema provides.

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 'Create a new project' clearly states the action and resource, but it does not differentiate from sibling creation tools (e.g., create_application) beyond the resource name.

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 is provided on when to use this tool versus alternatives like update_project or delete_project, nor are prerequisites or context mentioned.

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/kof70/coolify-mcp-server'

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