Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-deploy

Idempotent

Deploy an application to a Dokploy instance by application ID, with optional title and description to track deployment context.

Instructions

POST /application.deploy

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

Input Schema

NameRequiredDescriptionDefault
titleNo
descriptionNo
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 already declare openWorldHint=true and idempotentHint=true, so the safety/idempotency profile is partly covered. The description adds nothing beyond the raw endpoint: no side effects, no requirement that the application exists or has a configured build source, no indication of async behavior or what happens on repeated calls. It does not contradict 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?

A single line with no wasted words, but it is under-specified rather than concise; that line is not front-loaded with any useful information beyond the route itself.

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, three-parameter deployment tool with no output schema and zero parameter documentation, the description leaves nearly everything an agent needs unanswered.

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 (applicationId, title, description). The description names no parameters and gives no hint about what title/description do in a deploy operation, so it completely fails to compensate for the undocumented schema.

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.deploy" essentially restates the tool name plus an HTTP method; it never says in words what deploying an application means or what it produces. An agent can guess it triggers a deployment, but nothing distinguishes this from siblings like application-redeploy or application-deployNginxQuickstart.

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, and no mention of any alternative despite siblings such as application-redeploy, application-cancelDeployment, and application-killBuild that clearly compete for related intents. The agent must infer routing entirely from names.

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