Skip to main content
Glama
MCP Dokploy Online
by igoruam

mounts-create

Create a bind, volume, or file mount for a Dokploy service by defining its type, mount path, and target service ID.

Instructions

POST /mounts.create

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": {
      "type": "<type>",
      "mountPath": "<mountPath>",
      "serviceId": "<serviceId>"
    },
    "name": "mounts-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
contentNo
filePathNo
hostPathNo
mountPathYes
serviceIdYes
volumeNameNo
serviceTypeNo

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?

The only annotation is openWorldHint=true, so the description carries the full burden for a mutating operation and discloses nothing. It does not say what happens on duplicate mountPath, whether host paths must pre-exist, what permissions are required, or whether the operation is idempotent. An HTTP verb plus path is not behavioral disclosure.

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 only because it is under-specified rather than economical; a bare endpoint string is not a structured description. There is no front-loaded purpose statement or usage note to earn its place.

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 an 8-parameter create operation with conditional fields, no output schema, and near-zero annotation coverage, the definition is completely inadequate. Nothing tells an agent how to construct a valid call beyond the JSON schema's type constraints.

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?

Eight parameters with 0% schema description coverage, and the description supplies zero parameter meaning. The critical semantics — how `type` (bind/volume/file) interacts with the conditional fields hostPath, volumeName, filePath, and content — are entirely undocumented, leaving the agent to guess which fields are valid for which type.

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 endpoint string "POST /mounts.create", which restates the tool name rather than stating in plain language what the tool does or what a mount is. An agent can infer creation of a mount, but nothing distinguishes it from siblings like mounts-update, mounts-remove, or compose-loadMountsByService.

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 alternatives. The agent is given no basis for choosing between this and the other mount tools (mounts-update, mounts-remove, mounts-one, mounts-listByServiceId).

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