Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-move

Idempotent

Moves a MongoDB instance to a target environment by ID, enabling database relocation when changing deployment environments.

Instructions

POST /mongo.move

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>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "mongo-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
mongoIdYes
targetEnvironmentIdYes

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 only declare openWorldHint and idempotentHint, leaving destructive/read-only semantics and side effects undocumented. The description adds at most the fact that this is a POST mutation; it says nothing about what happens to the instance during a move, whether it must be stopped, whether the source environment is cleared, or whether the operation is reversible.

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: a single route fragment with no front-loaded statement of purpose. Nothing is wasted because almost nothing is there.

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 a two-parameter mutation on a database instance, with no output schema and sparse annotations, the description supplies none of the missing context. An agent cannot determine preconditions, effects, or return behavior from it.

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 both required parameters, and the description does not mention mongoId or targetEnvironmentId at all. An agent gets no meaning, format, or constraint information for either argument beyond the bare property 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?

"POST /mongo.move" only restates the tool name and HTTP route. It never says what a move actually does (reassign a Mongo instance to another environment?) or how it differs from siblings like mongo-deploy or mongo-create. The only new information is that the operation is invoked via POST.

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 such as mongo-deploy or application-move. An agent must guess entirely from the name whether this is the correct tool and in what circumstances it applies.

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