Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-one

Read-onlyIdempotent

Fetches details for a specific Dokploy server by ID, enabling you to inspect its configuration and status before managing deployments or infrastructure.

Instructions

GET /server.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": {
      "serverId": "<serverId>"
    },
    "name": "server-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 structurally. The description adds nothing beyond that — no statement about what a lookup returns, whether a missing server errors or returns empty, or what openWorld access implies.

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 shortness here reflects under-specification rather than economy — a bare route string with no front-loaded statement of purpose. Nothing in the string earns its place as guidance.

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 one-parameter read tool with no output schema, the description should at minimum say what entity is fetched and what shape of data comes back. Neither is present, and with 0% parameter coverage the definition is inadequate for correct invocation.

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 schema supplies only type and minLength. The description does not explain what the identifier refers to, its format, or where an agent would obtain one, leaving the parameter undocumented in both places.

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.one" is essentially a restatement of the tool name as an HTTP route, with no verb-plus-resource phrasing an agent can act on. Only by inference from the sibling "server-all" can one guess this fetches a single server record; the description itself never says what resource is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 the sibling "server-all" or any other alternative, and no stated precondition. The agent must infer usage entirely from the name and the required serverId parameter.

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