Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-listZones

Read-onlyIdempotent

Lists DNS zones for a specified DNS provider in Dokploy so you can inspect and manage domains tied to that provider.

Instructions

GET /dnsProvider.listZones

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-listZones"
  }
}

Input Schema

NameRequiredDescriptionDefault
dnsProviderIdYes

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 safety is covered. The description adds nothing beyond the redundant GET verb — no note on whether it calls out to the provider over the network, whether it paginates, or what happens with an invalid dnsProviderId.

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 short but not concisely informative — it is a route string rather than a front-loaded purpose statement. Brevity here reflects under-specification rather than efficiency.

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 and a 0%-documented required parameter, the description should define scope, return shape and failure behavior, and it does none of these. Only the annotations save the definition from being entirely opaque.

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?

Schema description coverage is 0% for the single required parameter dnsProviderId, so the description must compensate and does not. The parameter's self-explanatory name is the only aid; there is no statement of expected format or how the ID is obtained.

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 "GET /dnsProvider.listZones", which merely restates the tool name plus a method. It does imply listing DNS zones, but no plain-language statement of what is returned or scoped distinguishes it from siblings like dnsProvider-listRecords or dnsProvider-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 mention of alternatives such as dnsProvider-listRecords or dnsProvider-one, and no prerequisites or exclusions. The agent must infer everything from the 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