Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-redeploy

Idempotent

Trigger a redeployment for an existing Dokploy application by providing its application ID. Use it to apply configuration or code updates without creating a new application.

Instructions

POST /application.redeploy

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

Input Schema

NameRequiredDescriptionDefault
titleNo
descriptionNo
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the bar is lower, yet the description adds no behavioral context whatsoever: it does not say whether the redeploy restarts containers, interrupts running traffic, requires a prior build, or how long it takes. Nothing beyond the structured annotations is disclosed.

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 brevity here reflects under-specification rather than concision; a bare route string is not front-loaded information 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 mutating, open-world redeploy operation with three undocumented parameters and no output schema, the definition provides essentially nothing an agent needs to invoke it safely or correctly.

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 three parameters, so the description carries the full burden and contributes nothing. It never explains what applicationId refers to, nor why a redeploy would accept title/description, which is non-obvious and unexplained.

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 raw route "POST /application.redeploy", which merely restates the tool name as an HTTP endpoint. It implies a redeploy action but never states what gets redeployed, in what scope, or how it differs from siblings such as application-deploy or compose-redeploy.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives like application-deploy or application-reload. The agent must infer everything from the tool name alone.

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