Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-create

Creates a DNS provider configuration in Dokploy so deployments can manage DNS records and domains.

Instructions

POST /dnsProvider.create

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": {
      "name": "<name>",
      "config": "<config>"
    },
    "name": "dnsProvider-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
configYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

The only annotation is openWorldHint=true, so the description carries nearly the full behavioral burden and provides none of it. It does not disclose whether config requires credentials, whether creation validates connectivity, whether the operation is idempotent, or what happens on failure.

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 but by under-specification rather than concision; a raw route string is not a useful sentence. There is no front-loaded purpose statement the agent can act on.

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?

A creation tool with a free-form required config object, no output schema, and no field documentation needs substantial explanation of the config shape and side effects. The definition supplies none of it.

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?

Schema description coverage is 0% for both required parameters, and config is an untyped free-form object with additionalProperties:{} — the description does not explain a single key the agent must supply. This is the worst case: two required params, zero documentation in either schema or description.

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 "POST /dnsProvider.create", which restates the tool name and HTTP method rather than explaining what a DNS provider record is or what creating one entails. An agent learns only that this is a create operation, nothing about the resource's role among the dnsProvider siblings.

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 prerequisites, and no differentiation from siblings such as dnsProvider-update or dnsProvider-testConnection. The agent must infer entirely from the name that this is the first step before configuring records or zones.

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