Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-getDefaultCommand

Read-onlyIdempotent

Retrieve the default command configured for a specific Dokploy server by server ID, so you can inspect or reuse the command when managing deployments and infrastructure.

Instructions

GET /server.getDefaultCommand

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-getDefaultCommand"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/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 structured data — no note on what the returned command is used for, whether it depends on server state, or what happens with an invalid serverId.

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 with no wasted words, but that brevity comes from under-specification rather than efficiency; a raw route string conveys nothing an agent could not already read in the name.

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 tool with an undocumented required parameter and no output schema, the description should at least state what is produced and the identity of the referenced server. As written, an agent could not predict the response shape or confidently supply serverId.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single serverId parameter has 0% schema description coverage, so the description was the only place to explain what identifier is expected (name, UUID, hostname) and how invalid IDs are handled. It provides none of that, leaving the lone parameter 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 description is just the HTTP route "GET /server.getDefaultCommand", which restates the tool name rather than explaining what a default command is or what the tool returns. An agent learns only that it is a read-style endpoint on a server resource, nothing about the semantics of 'default command'.

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 mention of prerequisites, and no differentiation from any of the many sibling tools (e.g. server-one, compose-getDefaultCommand, server-getServices). The agent must infer the purpose entirely from the name.

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