Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-getServices

Read-onlyIdempotent

Retrieve services for a specified Dokploy server by server ID to inspect deployed workloads and manage infrastructure.

Instructions

GET /server.getServices

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": {
      "serverId": "<serverId>"
    },
    "name": "server-getServices"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

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; the description adds nothing on top of them — no note that it queries a remote Docker host, no error behavior (e.g., unknown serverId), no indication of payload size. It is a pure endpoint echo.

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 that is under-specification rather than conciseness — a raw route string with no front-loaded statement of purpose. Nothing in it earns its place as documentation.

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 tool that reaches an external Docker daemon and requires a specific identifier, the definition provides no context at all: no return shape, no failure modes, no scoping. It is completely inadequate despite the small surface area.

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?

The single required parameter serverId has 0% schema description coverage and the description adds no meaning — no hint whether it is a server name, numeric ID, or UUID, and no note about behavior when the ID is unknown.

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?

"GET /server.getServices" only restates the tool name as an HTTP route. It conveys that this is a read of something called 'services' for a server, but never says what a service is here, what the response contains, or how it differs from siblings like compose-loadServices or overview-services.

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?

No when-to-use guidance, no prerequisites, no mention of alternatives. The agent must infer usage entirely from the name and the crowded sibling list (server-all, server-one, compose-loadServices, etc.).

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