Skip to main content
Glama

create_environment

Create a new environment (e.g., production, staging) within a specified project using the project UUID and environment name.

Instructions

Create a new environment in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_uuidYesProject UUID
nameYesEnvironment name (e.g., production, staging)

Implementation Reference

  • Handler for create_environment tool: validates required params (project_uuid, name) and sends a POST request to /projects/{project_uuid}/environments to create the environment.
    case 'create_environment':
      requireParam(args, 'project_uuid');
      requireParam(args, 'name');
      return client.post(`/projects/${args.project_uuid}/environments`, args);
  • Schema definition for create_environment tool: requires project_uuid and name as string inputs.
    {
      name: 'create_environment',
      description: 'Create a new environment in a project',
      inputSchema: {
        type: 'object',
        properties: {
          project_uuid: { type: 'string', description: 'Project UUID' },
          name: { type: 'string', description: 'Environment name (e.g., production, staging)' }
        },
        required: ['project_uuid', 'name']
      }
    },
  • TypeScript interface for CreateEnvironmentInput, defining the shape of input data for creating an environment.
    export interface CreateEnvironmentInput {
      project_uuid: string;
      name: string;
    }
  • src/index.ts:36-38 (registration)
    Tool registration via MCP ListToolsRequestSchema handler which returns all tool definitions (including create_environment) via getToolDefinitions().
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: getToolDefinitions()
    }));
  • Helper function used by the create_environment handler to validate that required parameters are provided.
    function requireParam(args: ToolArgs, param: string): void {
      if (!args[param]) {
        throw new McpError(ErrorCode.InvalidParams, `${param} is required`);
      }
    }
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 only says 'create' without disclosing any behavioral traits like idempotency, permission requirements, or side effects (e.g., whether duplicate names cause errors).

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 that conveys the core purpose. It is front-loaded and contains no superfluous words, though it could afford to include slightly more context without losing conciseness.

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

Completeness3/5

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

For a simple tool with two required parameters and no output schema, the description is adequate but minimal. It does not cover behavior like naming restrictions or error conditions, which would improve completeness.

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?

The input schema covers both parameters with descriptions. The tool description adds no extra meaning beyond what the schema already provides, so baseline 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 clearly states the verb 'create', the resource 'environment', and the scope 'in a project'. It distinguishes from siblings like 'delete_environment' and 'get_environment'.

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 such as 'create_application_env' or other create tools. The description lacks context on prerequisites or conditions.

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