Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-completeOnboarding

Idempotent

Marks a Dokploy project onboarding as complete, enabling setup workflows to move from initial configuration to deployment management.

Instructions

POST /project.completeOnboarding

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project-completeOnboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

The description discloses no behavior beyond what the annotations and name already imply. It does not say what state changes on the project, whether the action is reversible, what errors occur if onboarding is already complete, or what is returned — critical gaps for a mutation endpoint with only idempotentHint and openWorldHint declared.

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 only because it is under-specified rather than economical — a single route string with no front-loaded explanation of intent or effect. Length is not the problem; absence of content is.

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 state-changing project operation with no output schema, the description supplies none of the context an agent needs to call it safely or correctly. Nothing explains the outcome, side effects, or how it relates to the onboarding-status sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is fully covered, so there is nothing for the description to clarify beyond what already exists. Baseline 4 applies when there are no parameters.

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 is a bare HTTP route restatement ('POST /project.completeOnboarding') that adds nothing to the tool name. An agent can guess this finalizes a project's onboarding, but nothing states what 'complete onboarding' actually does or how it differs from the sibling project-onboardingStatus.

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?

No when-to-use guidance, no prerequisites, no exclusions, and no mention of the closely related project-onboardingStatus tool. The agent is left to infer the entire usage context from the endpoint path.

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