Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-deploy

Idempotent

Deploy a MongoDB database instance on Dokploy by providing its database ID. Use this to start or trigger the deployment of an existing MongoDB service.

Instructions

POST /mongo.deploy

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

Input Schema

NameRequiredDescriptionDefault
mongoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.1/5.0
Behavior1/5

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

Annotations declare openWorldHint and idempotentHint but say nothing about whether this mutates state, what it destroys, whether it requires a prior mongo-create, or how long it takes. The description adds zero context beyond annotations, leaving a mutation-capable deployment operation entirely opaque.

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 short, but its brevity comes from under-specification rather than efficiency. A bare route string carries no front-loaded intent an agent can act on.

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?

No output schema, no annotations covering mutation semantics, and an undocumented required parameter mean the definition is wholly inadequate for an agent to call this safely or correctly.

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?

The single required parameter mongoId has 0% schema description coverage, and the description says nothing about it. With low coverage the description is expected to compensate, and it does not.

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?

The description is only "POST /mongo.deploy", which restates the tool name and HTTP method without saying what a deploy actually does (create, provision, restart, publish config?). It gives an agent no basis for distinguishing it from mongo-create, mongo-rebuild, or mongo-reload.

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 reference to any alternative sibling such as mongo-create or mongo-rebuild. The agent must guess entirely.

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