Skip to main content
Glama
MCP Dokploy Online
by igoruam

environment-create

Creates a new Dokploy project environment from a required name and project ID, with an optional description.

Instructions

POST /environment.create

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "projectId": "<projectId>"
    },
    "name": "environment-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
projectIdYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only openWorldHint=true, so the description carries the full burden and delivers nothing: no statement of side effects, whether the environment is immediately deployable, required permissions, or whether name must be unique. The endpoint string conveys no behavioral context beyond the HTTP verb.

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

Conciseness2/5

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

The single line is certainly short, but its brevity comes from under-specification rather than economy. It is not front-loaded with purpose, and the one piece of information given, an HTTP path, is of little use to an agent invoking a typed tool.

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?

For a creation tool with a required reference to another resource (projectId), no output schema, and near-zero annotation coverage, the definition should explain return identity, uniqueness, and failure modes. It provides none of this, leaving an agent unable to call it correctly beyond guessing from field names.

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?

Schema description coverage is 0% for three parameters, and the description compensates for none of it. It says nothing about what 'name' constrains, what 'projectId' must reference, or how 'description' is used, and additionalProperties=false means a caller has no guidance on allowed extras.

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

Purpose2/5

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

The description only restates the tool name as an HTTP route ("POST /environment.create"), which is a tautology rather than an explanation. It never states what an environment is in this system or what creating one accomplishes, though the verb+resource pairing at least matches the name.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when a caller should pick this over the many sibling *-saveEnvironment tools that also provision environments. The agent is left to guess entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools