Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-markRunning

Idempotent

Marks a specified Dokploy application as running using its application ID, updating its deployment status through the API.

Instructions

POST /application.markRunning

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-markRunning"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so the safety profile is partially covered without the description. The description adds nothing beyond them: no statement of what state is changed, whether it affects deployments, what permissions are required, or what happens if the application is already running. Nothing contradicts the annotations.

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 text is short but that brevity is under-specification, not conciseness. A raw method-plus-route string is not front-loaded explanatory content and provides no sentence an agent can 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?

For a state-mutating operation with no output schema and an undocumented parameter, the description is essentially empty. An agent cannot determine preconditions, side effects, or expected outcome before invoking it.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, applicationId, so the description carries the full burden of explaining it. It supplies no format, source, or constraint information — not even that it identifies the target application — leaving the agent to infer everything from the property name.

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 /application.markRunning" restates the tool name as an HTTP verb and path rather than describing the operation. An agent learns only that a POST is issued; it is never told what 'markRunning' means for an application's state or why one would do it instead of application-start.

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, when-not-to-use, or alternative guidance of any kind. With siblings like application-start, application-stop, application-redeploy, and application-reload, the agent has no basis for choosing this tool over them.

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