Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-create

Creates a new project in your Dokploy instance by specifying a name, with optional environment and description fields, so you can organize deployments and infrastructure resources.

Instructions

POST /project.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>"
    },
    "name": "project-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
nameYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations only supply openWorldHint=true; there is no readOnly/destructive hint, so the description should carry the mutation profile. It does not state whether the call is idempotent, what permissions are required, what happens on duplicate name, or what the response contains.

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?

It is short, but that is under-specification rather than conciseness: a bare route string that earns no informational value and gives the agent nothing front-loaded to act on.

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?

A three-parameter mutation tool with no output schema, no parameter documentation, and minimal annotations requires far more description than a single route path. Nothing an agent needs to call it correctly is present.

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% and the description says nothing about name, env, or description. An agent must reverse-engineer the meaning of env (environment slug? id?) and whether description is nullable entirely from the schema types.

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?

"POST /project.create" merely restates the tool name and HTTP verb; it never says what a project is or what creating one entails. There is no differentiation from siblings such as project-duplicate, project-update, or the many other *-create tools in the catalog.

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 when-to-use guidance, no prerequisites, no mention of alternatives (e.g. project-duplicate or environment-create) and no exclusions. The agent is left to infer intent purely from the tool 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