Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-all

Read-onlyIdempotent

Fetches all servers from your Dokploy instance so you can review infrastructure inventory and manage deployments.

Instructions

GET /server.all

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "server-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 and idempotency profile is fully covered structurally. The description adds nothing beyond that — no statement of result size, pagination, ordering, or whether it is scoped to the caller's organization.

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 brief to the point of under-specification: a single raw endpoint path with no verb-object framing an agent can act on. Brevity here reflects missing content rather than efficient editing.

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?

With no output schema and no description of the return payload, an agent cannot know what fields come back or how large the result is. For an unfiltered "all" listing inside a large sibling catalog, that gap matters.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. Baseline for a 0-parameter tool applies even though the description is bare.

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.all" restates the tool name as an HTTP method plus path rather than describing the action. An agent can infer it lists servers, but nothing states what a "server" is here or what the list contains, and it is not distinguished from siblings like server-allForPermissions or deployment-allByServer.

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?

No when-to-use guidance is given, and no alternative is mentioned. The agent is left to guess whether this is the right call versus the other server- and deployment-scoped list endpoints.

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