Skip to main content
Glama
MCP Dokploy Online
by igoruam

destination-all

Read-onlyIdempotent

Retrieves all deployment destinations registered in Dokploy so you can inspect or select the infrastructure targets available for your projects.

Instructions

GET /destination.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": "destination-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=true, openWorldHint=true, and idempotentHint=true, so the safety and idempotency profile is covered structurally. The description adds nothing beyond that – no return shape, pagination, volume, or scope (org/project) information. For an open-world list endpoint, this is a meaningful gap.

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 very short, but this is under-specification rather than conciseness. "GET /destination.all" is not a front-loaded explanation and does not tell the agent what the operation enumerates.

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 parameters and no output schema, nothing else documents the resource or response. An agent still doesn't know what a "destination" is here, what the payload looks like, or typical result sizes – gaps the description should fill for a simple list tool.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The empty schema is fully specified and 100% covered. No credit for added meaning because none is possible, but no penalty either.

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 "GET /destination.all" – it restates the endpoint/name rather than stating what the tool does, e.g. list all destinations. An agent must infer intent from the name alone, and nothing distinguishes the scope from destination-one or destination-create beyond the path token.

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 and no mention of alternatives. Nothing says when to prefer this over destination-one or why you would enumerate all destinations. The definition itself provides zero routing context.

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