Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-start

Idempotent

Starts a MongoDB instance in Dokploy by its mongoId, helping you resume database service during deployment or recovery.

Instructions

POST /mongo.start

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

Input Schema

NameRequiredDescriptionDefault
mongoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so the agent knows repeated calls are safe and the operation touches external state, but the description adds nothing about what starting entails, whether the instance must be stopped first, how long it takes, or what the response contains. For a state-changing lifecycle operation, that is a substantial 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?

There is nothing to trim, but brevity here reflects under-specification rather than efficiency. A bare route string is not a front-loaded summary of purpose and behavior.

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 no output schema, no parameter documentation, and only minimal annotations, the description carries most of the disclosure burden and supplies none of it. An agent cannot tell what will happen to the mongo instance, what errors to expect, or what the identifier refers to.

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 required parameter mongoId has 0% schema description coverage, and the description does not explain whether it is a database name, an instance/resource ID, or a UUID-style identifier. With one undocumented parameter, the description should have compensated and does not.

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 text is essentially the HTTP route restated: "POST /mongo.start" telegraphs a start action on a mongo resource, but it is a tautology of the tool name rather than a description of what starting does. It does not distinguish itself from siblings such as mongo-stop or mongo-redeploy beyond the verb embedded in the route.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g., only on a stopped instance). The only implied context comes from the name contrasting with mongo-stop, which is inference rather than stated guidance.

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