Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-byComposeId

Read-onlyIdempotent

Retrieves the domains configured for a specific Dokploy Compose service, letting you check which hostnames are attached to that deployment by its Compose ID.

Instructions

GET /domain.byComposeId

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": {
      "composeId": "<composeId>"
    },
    "name": "domain-byComposeId"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes

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, idempotentHint, and openWorldHint, so the safety profile is covered without the description. The description adds nothing beyond that — no note on what happens when the compose ID is unknown, whether a single domain or a list is returned, or any auth requirement — so it does not contradict the annotations but contributes no behavioral context.

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 single line is short but not concise in the useful sense: it contains no front-loaded purpose statement and is under-specified rather than economical. Every character merely repeats the endpoint path already implied by the tool name.

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, the description is the only place to learn what a domain lookup returns, and it says nothing about response shape, cardinality, or error behavior on a missing compose ID. For a lookup tool in a crowded domain family, that leaves the definition insufficient to call correctly with confidence.

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?

There is one required parameter with 0% schema description coverage, so the description must compensate and does not. The name "byComposeId" loosely implies the parameter identifies a compose, but the description gives no format, source, or example value to distinguish a compose ID from an application ID or name.

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 string "GET /domain.byComposeId", which essentially restates the tool name in HTTP form. An agent can infer it retrieves a domain record keyed by compose ID, but no verb-plus-resource statement clarifies the returned resource or how it differs from siblings such as domain-one or domain-byApplicationId.

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 alternatives, and no preconditions. Because the sibling list contains several overlapping domain lookups, an agent gets no signal about when a by-compose lookup is preferable to domain-one or domain-byApplicationId.

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