Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-reload

Idempotent

Reload a Dokploy application by its ID and name to apply configuration or environment changes without a full redeploy.

Instructions

POST /application.reload

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

Input Schema

NameRequiredDescriptionDefault
appNameYes
applicationIdYes

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 openWorldHint=true and idempotentHint=true but are silent on read-only vs destructive, so the description should have stated whether reloading interrupts a running application or discards state. It discloses none of that, offering only the HTTP verb, so beyond the annotations the agent learns nothing about outage risk or side effects.

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?

Brevity here is under-specification rather than efficiency; the single HTTP path token is not front-loaded useful information for an agent selecting a tool. There is no structure to speak of.

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 mutating application-lifecycle operation with two undocumented required parameters, no output schema, and only partial annotations, the definition is far too thin. Nothing tells the agent what a successful reload returns or how to confirm it happened.

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% for two required parameters (appName, applicationId), and the description adds no meaning: no format for applicationId, no relationship between appName and applicationId, no statement of whether both must match an existing app.

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 only the HTTP route "POST /application.reload", which merely restates the tool name in endpoint form. It does not say what a "reload" actually does (restart containers? re-pull config? zero-downtime?), nor does it distinguish this from siblings like application-redeploy or application-deploy.

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 guidance, no prerequisites, and no mention of when to prefer application-redeploy, application-deploy, or application-cancelDeployment. An agent must guess whether reload is the right operation at all.

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