Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-update

Idempotent

Update an existing MongoDB service in Dokploy by ID, changing settings such as Docker image, environment variables, credentials, replicas, resource limits, and swarm configuration.

Instructions

POST /mongo.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": {
      "mongoId": "<mongoId>"
    },
    "name": "mongo-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
argsNo
nameNo
appNameNo
commandNo
mongoIdYes
cpuLimitNo
replicasNo
createdAtNo
modeSwarmNo
networkIdsNo
descriptionNo
dockerImageNo
labelsSwarmNo
memoryLimitNo
replicaSetsNo
databaseUserNo
externalPortNo
networkSwarmNo
ulimitsSwarmNo
environmentIdNo
cpuReservationNo
placementSwarmNo
databasePasswordNo
healthCheckSwarmNo
applicationStatusNo
endpointSpecSwarmNo
memoryReservationNo
updateConfigSwarmNo
restartPolicySwarmNo
rollbackConfigSwarmNo
detachDokployNetworkNo
stopGracePeriodSwarmNo

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 declare openWorldHint=true and idempotentHint=true, but the description adds nothing about what an update does to the running container, whether it triggers a redeploy or restart, whether omitted fields are cleared or preserved, or what permissions are needed. With a mutation tool whose annotation set does not even include destructiveHint, this is a serious disclosure gap.

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 it is under-specification rather than conciseness — a single HTTP verb-plus-route string that front-loads nothing useful for an agent. There is no structure to speak of.

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 33-parameter mutation with no output schema, no annotations covering safety, and 0% schema documentation demands substantial prose, and this definition supplies none. An agent could not call it correctly without reverse-engineering the payload shape from field names alone.

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 33 parameters, with only mongoId required, so a large field like modeSwarm, updateConfigSwarm, or healthCheckSwarm carries no meaning from either the schema or the description. This is exactly the case where the description must compensate, and it does not attempt to.

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 'POST /mongo.update', which essentially restates the tool name in HTTP form. It implies a mutation on a Mongo resource, but says nothing about what aspect is updated (image, replicas, network, credentials) or how it differs from siblings such as mongo-create or mongo-deploy.

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 prerequisites, and no mention of alternatives such as mongo-create for new resources or the narrower helpers like mongo-saveExternalPort and mongo-changePassword. The agent must infer everything from the name and the 33-property schema.

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