Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-saveEnvironment

Idempotent

Save environment variables for a MongoDB instance in Dokploy by supplying its ID and environment configuration.

Instructions

POST /mongo.saveEnvironment

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>",
      "env": "<env>"
    },
    "name": "mongo-saveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
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?

The only disclosed behavior is the HTTP verb, and annotations provide merely openWorldHint and idempotentHint. The description says nothing about whether this overwrites existing variables, what happens to keys not included in `env`, required auth, or error behavior. The literal "POST" phrasing also sits uneasily with idempotentHint=true, though as a route path it is not a behavioral claim.

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 and front-loaded, but only because no content was written; the single route string carries no information an agent cannot already read from the name. Being terse is not a virtue when the remaining space is empty.

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?

A two-parameter mutation with no output schema, no parameter documentation, and minimal annotations requires the description to carry the load. It supplies none of the information needed to invoke this correctly or 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 both required parameters. The description does not explain that `mongoId` identifies the target Mongo service or what format `env` takes (dotenv text, JSON, key-value list) and what its nullable type implies for clearing configuration.

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.saveEnvironment", which restates the tool name rather than stating what it does. An agent can infer it writes some environment configuration for a Mongo resource, but nothing about what an "environment" is, what gets saved, or how this differs from the sibling environment-save 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 prerequisite or exclusion, and no reference to any of the sibling saveEnvironment variants or environment-create/environment-update alternatives. The agent is left to 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