Skip to main content
Glama
MCP Dokploy Online
by igoruam

mounts-update

Idempotent

Update an existing Dokploy mount by ID, changing its type, host path, mount path, volume name, file content, or linked service so container storage settings stay correct.

Instructions

POST /mounts.update

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": {
      "mountId": "<mountId>"
    },
    "name": "mounts-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
contentNo
mongoIdNo
mountIdYes
mysqlIdNo
redisIdNo
filePathNo
hostPathNo
libsqlIdNo
composeIdNo
mariadbIdNo
mountPathNo
postgresIdNo
volumeNameNo
serviceTypeNo
applicationIdNo

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 only supply openWorldHint and idempotentHint plus a title; the description adds no behavioral context whatsoever. For a mutation endpoint it does not state whether fields are partially or fully replaced, what happens to omitted fields, whether the mount must already exist, or what the response contains.

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 certainly short, but its brevity comes from under-specification rather than economy of expression. A raw route string is not meaningfully front-loaded content for an agent.

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?

With 16 parameters, one required identifier, two enums, no output schema, and only two weak annotations, the definition should explain far more than a route path. It leaves an agent unable to call the tool correctly without reverse-engineering the schema.

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 16 parameters, and the description provides no compensating explanation. Nothing indicates that mountId identifies the target, that serviceType/type enums select the mount variant, or how hostPath, mountPath, volumeName, and the various service-id fields relate to each other.

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 /mounts.update", which merely restates the tool name in transport notation. It conveys that this mutates a mount record but says nothing about what a mount is updated with or what result to expect, and gives no differentiation from siblings such as mounts-create or mounts-remove.

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 guidance on when to use this tool, no preconditions, and no mention of alternatives like mounts-create for new mounts or mounts-remove for deletion. 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