Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-changeStatus

Idempotent

Updates a MongoDB instance's application status by ID, setting it to idle, running, done, or error to reflect deployment or operation state.

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 observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the description's only contribution is the word POST, which weakly implies a state-changing call. It says nothing about what happens to the running database when status changes, whether the operation is disruptive, whether permissions are required, or what the response contains.

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 no wasted wording because there is almost no wording at all; the single route fragment is front-loaded but conveys nothing actionable. This is under-specification rather than conciseness.

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 required-parameter, state-mutating tool with no output schema and zero schema documentation, the definition leaves every question unanswered: target resource, valid transitions, and effects. It is not complete enough for an agent to invoke confidently.

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 description coverage is 0% for two required parameters, so the description carries the full burden and delivers nothing. It never explains what mongoId identifies or what the idle/running/done/error enum means in terms of allowed transitions or side effects.

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 route string "POST /mongo.changeStatus", which essentially restates the tool name and adds no verb+resource meaning. It does not say what entity's status is being changed (a Mongo database/instance), what 'status' represents, or how this differs from the many sibling *-changeStatus tools.

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 mention of alternatives such as mongo-start, mongo-stop, or mongo-update that an agent might otherwise pick. 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