Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-createRecord

Creates a DNS record for a specified zone and provider, using record type, name, content, TTL, and proxy settings to configure domain routing.

Instructions

POST /dnsProvider.createRecord

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": {
      "type": "<type>",
      "name": "<name>",
      "content": "<content>",
      "dnsProviderId": "<dnsProviderId>",
      "zoneId": "<zoneId>"
    },
    "name": "dnsProvider-createRecord"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
nameYes
typeYes
zoneIdYes
contentYes
proxiedNo
dnsProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

The only annotation is openWorldHint=true, which says nothing about mutation, idempotency, or required permissions. The description supplies no behavioral context at all: it does not say the record is written to a live zone, whether duplicate name/type pairs are rejected, whether changes propagate, or what authorization the DNS provider needs. For a write operation with essentially no annotation coverage, this is a total gap.

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 shortness here reflects under-specification rather than economy. A bare route string is not front-loaded information an 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 7-parameter, 5-required mutation tool with no output schema, no descriptive schema fields, and only openWorldHint in annotations needs substantial explanation. The description provides none, leaving the agent to guess at content semantics and mutation effects.

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% across 7 parameters, so the description must compensate and it does not. It says nothing about ttl units or defaults, what content means per record type (IP vs hostname vs TXT payload vs MX priority), the role of dnsProviderId versus zoneId, or what proxied does.

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?

"POST /dnsProvider.createRecord" only restates the tool name and its HTTP route; it never says in prose that it creates a DNS record in a zone. The verb+resource is recoverable from the identifier alone, so the description contributes no distinguishing information beyond what the name already gives.

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 statement of when to use this versus dnsProvider-updateRecord, dnsProvider-listRecords, or dnsProvider-create. The agent must infer from naming that this creates an individual record while the siblings update, list, or delete one.

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