Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-stop

Idempotent

Stops a MongoDB service in Dokploy using its mongoId to halt database operations for maintenance, cleanup, or resource management.

Instructions

POST /mongo.stop

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-stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
mongoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare openWorldHint=true and idempotentHint=true, so idempotency is already carried by structured data; the description adds no behavior of its own. It does not say whether the stop is graceful, whether data is preserved, whether the instance stops accepting connections, or whether permissions are required — all critical for a disruptive database 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?

At four words it is not bloated, but it is under-specified rather than concise: the entire payload is a route string that duplicates metadata. Nothing is front-loaded because there is no substantive content to order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Stopping a database is a consequential action with no output schema and no annotation covering destructiveness, yet the description supplies no information about side effects, downtime, or reversibility. For a one-parameter mutation-style endpoint, this leaves the agent largely uninformed beyond the tool name.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single mongoId parameter has 0% schema description coverage, so the description is the only place meaning could be added, and it adds nothing — no statement of whether this is an instance ID, name, or where to find it. The endpoint path gives no hint about the identifier's form.

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 /mongo.stop", which restates the tool name rather than explaining what stopping a Mongo instance entails. The verb+resource is inferable, but no scope, effect, or distinction from siblings like mongo-start is stated in the description itself.

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, when not to, or what to use instead (e.g., mongo-start to reverse it, or application-stop for other resources). The agent must infer everything from the 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