Skip to main content
Glama
MCP Dokploy Online
by igoruam

destination-one

Read-onlyIdempotent

Retrieves details for a specific Dokploy destination by its ID, enabling you to inspect deployment target configuration.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
destinationIdYes

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=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no note on error behavior for a missing destinationId, no authentication/scope requirements, and no indication of what the response contains. With annotation coverage the bar is lower, but zero added context still merits a low score.

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 extremely short but that brevity reflects under-specification rather than efficient communication. A bare endpoint string is not a front-loaded explanation of the tool's function.

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?

For a tool with one required parameter and no output schema, the description should at minimum explain that it fetches one destination by ID and what the ID refers to. None of that is present, leaving the definition inadequate for correct invocation.

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

Parameters1/5

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

The single parameter destinationId has 0% schema description coverage and the description says nothing about its format, source, or constraints. The required identifier is entirely undocumented in both the schema and the prose, so an agent has no guidance on what a valid value looks like.

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 raw endpoint reference "GET /destination.one", which restates the tool name and HTTP verb without stating that it retrieves a single destination record by identifier. An agent must infer from the name and the sibling destination-all that this is a single-item read. It is not misleading, but it conveys no purpose beyond what the name already says.

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 destination-all for listing or destination-update for mutation, and no prerequisites. The GET verb implies a read operation, but nothing in the text directs an agent to choose this tool over its siblings.

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