Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-start

Idempotent

Start a Dokploy application by its application ID to bring a stopped or inactive deployment back online.

Instructions

POST /application.start

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": {
      "applicationId": "<applicationId>"
    },
    "name": "application-start"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, and the description adds only the HTTP method, which is marginal beyond that. It does not say what state change occurs, what happens if the application is already running, what permissions/auth are needed, or what the response contains – all of which matter for a mutating start operation with no readOnly/destructive hint to lean on.

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?

Extremely short, but shortness here reflects under-specification rather than efficient structure: there is no front-loaded purpose statement, no scope, and no usage context, just a route stub.

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

Completeness2/5

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

Even for a simple one-parameter tool with no output schema, the description omits the outcome of the call, the state transition semantics, and any parameter meaning. Annotations cover only idempotency and open-world reach, leaving the core behavior undocumented.

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?

The single parameter applicationId has 0% schema description coverage, so the description must compensate, yet it says nothing about the parameter – no format, no sourcing (where to obtain the ID), no scoping semantics. The URL path fragment does not explain the parameter at all.

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 just "POST /application.start" – an HTTP method plus the endpoint path, which restates the tool name rather than explaining what starting means (launching a container? re-enabling a stopped app? triggering a build?). An agent cannot distinguish this from siblings like application-redeploy, application-reload, or compose-start based on this text.

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, and no mention of alternatives such as application-redeploy, application-reload, or the start tools for other resource types. The only implicit signal is the POST verb suggesting a mutating action.

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