Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-one

Read-onlyIdempotent

Retrieves details for a specific PostgreSQL database by ID in Dokploy, helping you inspect its configuration and status for infrastructure management.

Instructions

GET /postgres.one

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

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered; the description adds nothing beyond that — no return shape, no id format, no error or not-found behavior. With zero added context, the description contributes nothing the structured fields don't already say.

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?

The text is short, but it is under-specified rather than concise: a bare route string earns no place as a tool description. There is nothing to front-load because no meaningful content exists.

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 read tool with a required identifier and no output schema needs the description to explain what is returned and what the identifier means. The definition covers neither, so it is inadequate for correct invocation.

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?

There is one required parameter, postgresId, with 0% schema description coverage and no description text explaining it. The definition never states whether the ID is a UUID, slug, or name, nor where an agent would obtain one — the single required input is entirely undocumented.

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 entire description is the route string "GET /postgres.one", which merely restates the tool name with an HTTP verb attached. An agent can infer only that this performs a retrieval against a Postgres resource; it does not say whether it fetches configuration, status, connection details, or something else, and it does nothing to distinguish it from siblings like postgres-search or postgres-readLogs.

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 at all, no prerequisites, and no mention of any alternative tool. The agent is left to guess from the name alone whether this is the right way to inspect a Postgres instance versus postgres-search or postgres-readLogs.

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