Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-deployNginxQuickstart

Idempotent

Deploys a preconfigured Nginx application to a Dokploy environment in one call, so you can bootstrap a web server without manual setup.

Instructions

POST /application.deployNginxQuickstart

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": {
      "environmentId": "<environmentId>"
    },
    "name": "application-deployNginxQuickstart"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
environmentIdYes

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 agent knows the call reaches outside systems and can be retried. The description adds nothing beyond the POST method: it does not say whether resources are created or overwritten, whether an existing application with the same name is affected, or what the response contains — meaningful gaps for a deploy mutation.

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 is under-specification rather than conciseness. It is a single route string with no front-loaded statement of purpose or effect.

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?

This is a mutation tool with no output schema, zero parameter documentation, and only partial annotations, so the description carries the full explanatory burden and delivers none of it. Nothing tells the agent what the deploy produces, what prerequisites exist, or how to interpret success.

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 parameters, and the description supplies no parameter meaning whatsoever. It never mentions environmentId (required) or the optional serverId, so an agent must guess what a server ID even selects in the quickstart flow.

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.deployNginxQuickstart", which restates the tool name rather than explaining what the operation does. It implies an Nginx quickstart deployment via POST, but nothing about what gets deployed, to where, or what the outcome is.

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 at all, and no mention of the obvious alternatives among siblings such as application-deploy, ai-deploy, or compose-deploy. An agent cannot tell from this text why it would pick the Nginx quickstart over a general deploy.

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