Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-byApplicationId

Read-onlyIdempotent

Retrieve the domain associated with a specific Dokploy application using its applicationId, so you can identify or manage the domain assigned to that application.

Instructions

GET /domain.byApplicationId

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": {
      "applicationId": "<applicationId>"
    },
    "name": "domain-byApplicationId"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

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, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description contributes nothing beyond that—no note on what a missing/unknown applicationId yields, whether the result can be empty, or whether it hits an external domain server (relevant given openWorldHint=true).

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 unquestionably short, but the brevity is under-specification rather than conciseness; the single line is a route annotation with no informative content front-loaded for the agent.

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?

No output schema exists, so the description should hint at the return shape of this lookup, and it does not. For a required-identifier retrieval tool, the agent needs at minimum what is looked up by applicationId and what comes back, neither of which is stated.

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?

The single parameter applicationId has 0% schema description coverage, and the description does not compensate at all—it never explains what form of identifier is expected, whether it is an internal numeric ID or a UUID/string, or where the agent would obtain one.

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 HTTP route string 'GET /domain.byApplicationId', which restates the tool name rather than explaining what it does. An agent cannot tell from this whether it returns the domain assigned to an application, a list of domains, or domain configuration metadata, nor how it differs from domain-byComposeId or domain-one.

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

Usage Guidelines1/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 exclusions, and no mention of the sibling alternatives (e.g., domain-byComposeId for compose-scoped lookups, domain-one for other identifiers). The agent is left to infer everything from the tool name alone.

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