Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-saveDockerProvider

Idempotent

Saves Docker registry credentials and image settings for a Dokploy application, enabling deployments to pull from the configured registry.

Instructions

POST /application.saveDockerProvider

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": {
      "dockerImage": "<dockerImage>",
      "applicationId": "<applicationId>",
      "username": "<username>",
      "password": "<password>",
      "registryUrl": "<registryUrl>"
    },
    "name": "application-saveDockerProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
usernameYes
dockerImageYes
registryUrlYes
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only idempotentHint=true and openWorldHint=true; the description adds no behavioral context at all. It does not disclose that credentials (username/password) are sent, whether secrets are stored or encrypted, whether an existing Docker provider is overwritten, or what a successful save returns.

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?

There is no wasted detail, but this is under-specification rather than conciseness: a single endpoint token is not a description and gives the agent nothing front-loaded about the action or its inputs.

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?

A write operation taking five required parameters including credentials, with no output schema, no parameter documentation, and no annotations covering safety or effects. The definition is far too thin for an agent to invoke this 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?

Five required parameters with 0% schema description coverage, and the description mentions none of them. Nothing explains the expected format of registryUrl or dockerImage, or which applicationId scope applies, so the only information is the bare parameter names.

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 string "POST /application.saveDockerProvider", which restates the tool name rather than explaining the operation. It does not say whether this creates a new Docker provider, updates an existing one, or what happens when a provider already exists for the application.

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 usage guidance whatsoever: no when-to-use, no when-not-to-use, and no routing to the many siblings such as application-saveGitProvider or application-saveGithubProvider. An agent cannot tell from this definition why it would choose this provider saver over another.

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