Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-reload

Idempotent

Reloads a MongoDB instance for a specified Dokploy application using its Mongo ID and app name to apply configuration changes.

Instructions

POST /mongo.reload

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>",
      "appName": "<appName>"
    },
    "name": "mongo-reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
mongoIdYes

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 already declare openWorldHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds nothing beyond the verb "POST" — no word on downtime, whether the container restarts, whether config is re-read, or what happens to in-flight connections, all of which are central for a reload operation.

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 only four words, so there is no wasted prose, but the brevity is under-specification rather than economy. Nothing is front-loaded because there is effectively no content.

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 mutating, open-world operation with two fully undocumented required parameters and no output schema, the description provides no actionable context. An agent cannot safely decide when or how to invoke it from this definition 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?

Both required parameters (mongoId, appName) have 0% schema description coverage, and the description supplies no meaning for either. The agent must guess what mongoId identifies and how appName scopes the reload, so the description fails to compensate for the schema gap.

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.reload" merely restates the tool name as an HTTP route. It does not say what a reload actually does to the Mongo instance (restart the process, re-read config, re-apply deployment settings) or how that differs from siblings like mongo-rebuild, mongo-start, or mongo-stop.

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 indication of which sibling to pick instead. An agent facing mongo-rebuild, mongo-start, mongo-stop, and mongo-reload has nothing in this definition to disambiguate the choice.

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