Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-validate

Read-onlyIdempotent

Validate a Dokploy server by ID to check its configuration and connectivity before using it for deployments or infrastructure management.

Instructions

GET /server.validate

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

Input Schema

NameRequiredDescriptionDefault
serverIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered elsewhere. The description contributes nothing beyond that: it does not say what validation entails, whether it hits the network or a remote server, what happens if the server is unreachable, or what a failure signifies.

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 that brevity comes from under-specification rather than tight writing; a verbatim route string is not a useful front-loaded summary of the tool's behavior for an agent deciding whether to call it.

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?

With no output schema, the description is the only place an agent could learn what a successful or failed validation returns, and it says nothing. For a validation tool whose entire value is in interpreting the result, the definition is inadequate.

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?

Schema description coverage is 0% for the single required parameter serverId, so the description would need to carry the meaning of that identifier (server ID versus name or hostname, and which format is expected). It provides none, leaving the parameter documented only by its camelCase name and a minLength constraint.

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 endpoint string "GET /server.validate", which essentially restates the tool name and annotation title ("Server Validate") rather than stating in plain terms what is validated (connectivity, credentials, SSH key, configuration). An agent can guess this checks a server's status from the name, but the description adds no clarification.

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 on when to call this versus siblings such as domain-validateDomain, licenseKey-validate, or server-one. No prerequisites, no preconditions, and no exclusions are stated anywhere in the text.

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