Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-rebuild

Idempotent

Triggers a rebuild of a specified MongoDB instance in Dokploy by mongoId, redeploying the database service to recover from deployment issues.

Instructions

POST /mongo.rebuild

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

Input Schema

NameRequiredDescriptionDefault
mongoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations declare only idempotentHint=true and openWorldHint=true; nothing states whether a rebuild is destructive, whether it wipes data, what permissions it needs, or whether the resource stays available. The description adds no behavioral context whatsoever beyond the annotation hints, leaving a probably-destructive operation undisclosed.

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 shortness here reflects under-specification rather than economy: a bare route string with no front-loaded statement of purpose. Nothing in it earns or justifies the omission.

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 likely mutates or destroys a database instance, there is no output schema, no annotation for destructive behavior, and no descriptive compensation for the undocumented parameter. An agent cannot call this correctly or safely from the 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?

The single required parameter mongoId has 0% schema description coverage, and the description says nothing about it. It does not tell the agent what identifier is expected or what resource it must point at, so no meaning is added beyond the bare schema.

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.rebuild", which restates the tool name rather than explaining what rebuilding a Mongo resource does. There is no verb-plus-resource statement of effect, no mention of what is rebuilt or what happens to existing data.

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 when-to-use guidance, no prerequisites, and no reference to alternative tools such as mongo-reload, mongo-start, or mongo-stop. Note the sibling list is contextual only; even judged in isolation the description offers zero selection 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