Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-updateRecord

Idempotent

Update an existing DNS record in a specified provider and zone by record ID, letting you change its type, name, content, TTL, or proxy setting.

Instructions

POST /dnsProvider.updateRecord

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>",
      "recordId": "<recordId>"
    },
    "name": "dnsProvider-updateRecord"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
nameYes
typeYes
zoneIdYes
contentYes
proxiedNo
recordIdYes
dnsProviderIdYes

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?

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds nothing on top of them. It does not say whether the update replaces or merges fields, what permissions are needed, whether the TTL change affects propagation, or what the response contains. For a mutation endpoint with eight parameters, this is a complete behavioral void.

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 extremely short and contains no filler, but the brevity here reflects under-specification rather than economy. A bare HTTP path is not a useful front-loaded summary of a record update operation.

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?

With eight parameters, six of them required, zero schema descriptions, no output schema, and no annotations covering destructive effects, the definition is far too thin for the tool's complexity. An agent cannot determine required inputs or expected behavior from this description.

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 eight parameters, so the description carries the full burden of explaining them and supplies none. Nothing clarifies the difference between recordId and zoneId, the meaning of proxied, TTL constraints, or the valid record type enum values.

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.updateRecord", which merely restates the tool name plus an HTTP method. It implies an update of a DNS record but adds no verb-level specificity about what is updated or what scope the operation has, beyond what the name already tells the agent.

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 guidance on when to use this tool versus siblings such as dnsProvider-createRecord, dnsProvider-deleteRecord, or dnsProvider-update. No prerequisites, no exclusions, and no conditions are stated anywhere in the definition.

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