Skip to main content
Glama
Sign In
Dokploy MCP Server

Dokploy MCP Server

by bravos2k5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mongo-changeStatus

Idempotent

Change the status of a MongoDB database in Dokploy by providing its ID and the desired state (idle, running, done, error).

Instructions

POST /mongo.changeStatus

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>",
      "applicationStatus": "<applicationStatus>"
    },
    "name": "mongo-changeStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
mongoIdYes
applicationStatusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.29.1

TDQS

D1.3/5.0
Behavior2/5

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

Annotations provide idempotentHint and openWorldHint, but description adds no behavioral details beyond that. It doesn't describe side effects, required permissions, or state transitions.

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 description is a single sentence, but it is the endpoint string—concise but uninformative. It does not structure any useful information.

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 tool that changes status of a managed MongoDB resource, the description is completely inadequate. It omits prerequisites, valid transition paths, error behavior, and any output details.

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 coverage is 0% with no descriptions. The description fails to explain what mongoId represents or the meaning of applicationStatus enum values in context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description is just the endpoint 'POST /mongo.changeStatus', which tautologically restates the tool name. It does not specify what the tool does or what resource it operates on.

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?

No guidance on when to use this tool versus siblings like mongo-start, mongo-stop, or other changeStatus tools. The description offers no context for selection.

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