Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-reload

Idempotent

Reloads PostgreSQL configuration for a specified Dokploy database instance using its postgresId and appName, applying configuration changes without restarting the service.

Instructions

POST /postgres.reload

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>",
      "appName": "<appName>"
    },
    "name": "postgres-reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
postgresIdYes

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 already declare openWorldHint=true and idempotentHint=true; the description adds nothing beyond them. It does not disclose what a reload disrupts (connections, in-flight queries), what permissions are required, or whether the operation is async.

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 a single fragment with no wasted words, but that brevity reflects under-specification rather than tight writing; there is no front-loaded statement of effect.

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 mutating, open-world operation with two undocumented required parameters, no output schema, and only weak annotations, the definition supplies no operational context at all.

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, postgresId and appName, and the description does not mention them at all. The agent gets no clue about the expected identifier format or why appName is required alongside postgresId.

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 path 'POST /postgres.reload', which restates the tool name rather than describing what a reload does to a Postgres instance. It does not distinguish this from siblings like postgres-start, postgres-stop, or postgres-rebuild.

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 precondition, and no reference to any alternative tool. An agent cannot tell from this text whether reload should be preferred over restart-style siblings.

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