Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-update

Idempotent

Updates an existing Dokploy project by project ID, letting you change its name, environment, description, or organization so project metadata stays accurate.

Instructions

POST /project.update

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": {
      "projectId": "<projectId>"
    },
    "name": "project-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
nameNo
createdAtNo
projectIdYes
descriptionNo
organizationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations declare idempotentHint=true and openWorldHint=true but say nothing about read-only or destructive behavior, so the "POST" verb contributes a weak signal that this is a write. The description adds no information about permissions, partial vs full replacement of fields, or effects on unspecified properties.

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 only four words, so nothing is wasted, but this is under-specification rather than conciseness. There is no front-loaded statement of effect or scope to anchor the reader.

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 six-parameter mutation with no output schema and no parameter descriptions, the definition supplies nothing an agent needs to call it correctly, not even which fields are optional versus cleared when absent.

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% across six parameters, and the description mentions none of them. An agent cannot learn from it what 'env', 'organizationId', 'createdAt', or even the required 'projectId' mean or whether omitted fields are cleared or left untouched.

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.update" merely restates the tool name as an HTTP verb and route. It implies a mutation to an existing project but never says what aspects are updated or how it differs from siblings such as project-create or project-duplicate.

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?

The description gives no when-to-use guidance, no prerequisites (e.g. needing an existing projectId), and no mention of alternatives like project-create for new projects or project-remove for deletion.

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