Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-one

Read-onlyIdempotent

Retrieves a DNS provider's details by ID, enabling inspection of its configuration within Dokploy for deployment and infrastructure management.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
dnsProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the description's GET does not contradict them. However, the description adds no behavioral context of its own — no note on error behavior for unknown IDs, no indication of what record is returned, and no hint that this is a read-only single-record lookup.

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 short with no filler, but that brevity comes from under-specification rather than efficiency. The whole text is a URL fragment, not a front-loaded explanation of the tool's behavior.

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 lookup tool with an undocumented required identifier, no output schema, and no prose beyond the endpoint, an agent cannot tell what will be returned or when to prefer this over sibling listing tools. The definition is materially incomplete.

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 parameter (dnsProviderId) with 0% schema description coverage, so the description carries the full burden of explaining it and does not. It never clarifies whether the ID is the provider's numeric id, UUID, or slug, nor the consequences of passing an invalid identifier.

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 HTTP endpoint "GET /dnsProvider.one". The GET verb implies a read and "one" implies a single-resource fetch, but the resource type (DNS provider configuration) and the meaning of "one" are never stated in prose.

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?

No when-to-use guidance at all. Nothing distinguishes it from siblings such as dnsProvider-all or dnsProvider-listZones, and no prerequisites or conditions for choosing this retrieval are given.

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