Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-saveEnvironment

Idempotent

Save environment variables for a PostgreSQL service in Dokploy by passing postgresId and env, so database configuration changes are stored.

Instructions

POST /postgres.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": {
      "postgresId": "<postgresId>",
      "env": "<env>"
    },
    "name": "postgres-saveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
postgresIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations supply only openWorldHint and idempotentHint, and the description adds nothing beyond the route string. It does not say whether this creates or overwrites an environment, whether it is destructive to existing variables, what permissions are needed, or what is returned.

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 brevity here is under-specification rather than conciseness: a bare route string carries no front-loaded purpose statement or usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter mutation tool the definition is far from complete: no explanation of the env payload format, no mutation semantics, no output schema, and no differentiation from sibling saveEnvironment tools.

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?

Both required parameters (postgresId, env) have 0% schema description coverage, and the description provides no compensating meaning — not even the format of 'env' (raw env file text? JSON? key-value list?). This is a genuine gap the description should have filled.

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 /postgres.saveEnvironment", which essentially restates the tool name. It hints at saving an environment for a Postgres resource but gives no verb-level explanation of what is saved or how it differs from siblings like postgres-update or environment-update.

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 guidance whatsoever on when to call this versus the many sibling saveEnvironment variants (mysql, mariadb, redis, environment-update) or versus environment-create/update. No preconditions, no alternatives, no exclusions.

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