Skip to main content
Glama

Patch DNS record

patch_dns_record
DestructiveIdempotent

Update selected fields of an existing DNS record and keep all unspecified values unchanged.

Instructions

Change only some fields of an existing DNS record, e.g. just data or ttl. The current record is read first and every field you leave out keeps its stored value; when you change the type, give the new type's required fields too. Prefer this over update_dns_record. Returns the stored record.

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": {
      "domain_id": "<domain_id>",
      "record_id": "<record_id>"
    },
    "name": "patch_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
algNorequired for DS: the DNSSEC signing algorithm number, 0-255
tagNorequired for DS as a number (the key tag 0-65535 of the referenced DNSKEY) and for CAA as a string (the property tag, e.g. issue, issuewild or iodef)
ttlNotime-to-live in seconds, 60-604800, must be a multiple of 60, defaults to 3600
dataNothe record's main value: an IPv4 address for A, an IPv6 address for AAAA, a hostname for ANAME/CNAME/MX/NS/SRV, free text for TXT, the CAA property value, or the hex hash for DS/TLSA
hostNothe host/subdomain the record applies to, e.g. 'www' or '@' for the root
portNorequired for SRV: the port 0-65535 the service is found on
typeNothe record type
dtypeNorequired for TLSA: matching type of the hash in data (0 exact match, 1 SHA-256, 2 SHA-512)
flagsNorequired for CAA: 128 to mark the property critical, otherwise 0
usageNorequired for TLSA: certificate usage (0 PKIX-TA, 1 PKIX-EE, 2 DANE-TA, 3 DANE-EE)
digestNorequired for DS: digest type of the hash in data (1 SHA-1, 2 SHA-256, 4 SHA-384)
weightNorequired for SRV: relative weight 0-65535 among records with the same priority
priorityNorequired for MX and SRV: preference value 0-65535, lower is tried first
selectorNorequired for TLSA: what the hash is taken from (0 full certificate, 1 subject public key)
domain_idYesthe Domeneshop domain ID, from list_domains
record_idYesthe DNS record ID to change, from list_dns_records

Output Schema

NameRequiredDescriptionDefault
idNo
algNo
tagNo
ttlNo
dataYes
hostYes
portNo
typeYes
dtypeNo
flagsNo
usageNo
digestNo
weightNo
priorityNo
selectorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.7
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed27 schema fields changedv2.0.0
    • changedInput schema / properties / alg / description
      Previous value: -"required for DS: the DNSSEC signing algorithm number"New value: +"required for DS: the DNSSEC signing algorithm number, 0-255"
    • changedInput schema / properties / alg / maximum
      Previous value: -9007199254740991New value: +255
    • changedInput schema / properties / alg / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / data / description
      Previous value: -"the record's main value: an IP address for A/AAAA, a hostname for ANAME/CNAME/MX/NS/SRV, free text for TXT, the CAA property value, or the hex hash for DS/TLSA"New value: +"the record's main value: an IPv4 address for A, an IPv6 address for AAAA, a hostname for ANAME/CNAME/MX/NS/SRV, free text for TXT, the CAA property value, or the hex hash for DS/TLSA"
    • addedInput schema / properties / data / minLength
      Added value: +1
    • changedInput schema / properties / digest / maximum
      Previous value: -9007199254740991New value: +255
    • changedInput schema / properties / digest / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / dtype / maximum
      Previous value: -9007199254740991New value: +2
    • changedInput schema / properties / dtype / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / flags / maximum
      Previous value: -9007199254740991New value: +255
    • changedInput schema / properties / flags / minimum
      Previous value: --9007199254740991New value: +0
    • addedInput schema / properties / host / minLength
      Added value: +1
    • changedInput schema / properties / port / description
      Previous value: -"required for SRV: the port the service is found on"New value: +"required for SRV: the port 0-65535 the service is found on"
    • changedInput schema / properties / priority / description
      Previous value: -"required for MX and SRV: preference value, lower is tried first"New value: +"required for MX and SRV: preference value 0-65535, lower is tried first"
    • changedInput schema / properties / priority / maximum
      Previous value: -9007199254740991New value: +65535
    • changedInput schema / properties / priority / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / selector / maximum
      Previous value: -9007199254740991New value: +1
    • changedInput schema / properties / selector / minimum
      Previous value: --9007199254740991New value: +0
    • addedInput schema / properties / tag / anyOf
      Added value: +[
      +  {
      +    "maximum": 65535,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / tag / description
      Previous value: -"required for DS (the key tag of the referenced DNSKEY) and for CAA (the property tag, e.g. issue, issuewild or iodef)"New value: +"required for DS as a number (the key tag 0-65535 of the referenced DNSKEY) and for CAA as a string (the property tag, e.g. issue, issuewild or iodef)"
    • removedInput schema / properties / tag / type
      Removed value: -[
      -  "number",
      -  "string"
      -]
    • changedInput schema / properties / usage / maximum
      Previous value: -9007199254740991New value: +3
    • changedInput schema / properties / usage / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / weight / description
      Previous value: -"required for SRV: relative weight among records with the same priority"New value: +"required for SRV: relative weight 0-65535 among records with the same priority"
    • changedInput schema / properties / weight / maximum
      Previous value: -9007199254740991New value: +65535
    • changedInput schema / properties / weight / minimum
      Previous value: --9007199254740991New value: +0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "alg": {
      +      "type": "number"
      +    },
      +    "data": {
      +      "type": "string"
      +    },
      +    "digest": {
      +      "type": "number"
      +    },
      +    "dtype": {
      +      "type": "number"
      +    },
      +    "flags": {
      +      "type": "number"
      +    },
      +    "host": {
      +      "type": "string"
      +    },
      +    "id": {
      +      "type": "number"
      +    },
      +    "port": {
      +      "type": "number"
      +    },
      +    "priority": {
      +      "type": "number"
      +    },
      +    "selector": {
      +      "type": "number"
      +    },
      +    "tag": {
      +      "type": [
      +        "number",
      +        "string"
      +      ]
      +    },
      +    "ttl": {
      +      "type": "number"
      +    },
      +    "type": {
      +      "type": "string"
      +    },
      +    "usage": {
      +      "type": "number"
      +    },
      +    "weight": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "host",
      +    "type",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  3. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, but the description adds the crucial read-modify-write disclosure: the record is read first and omitted fields keep stored values. That materially changes the risk picture versus a blind mutation. It stops short of saying what happens if record_id does not exist or whether the type change discards previously set type-specific fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly four sentences, front-loaded with the core behavior, and every clause carries weight. The trailing "Returns the stored record" is mild duplication given an output schema exists, but it is one short sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter patch tool with full schema coverage, an output schema and annotations, the description supplies the semantics that structured fields cannot. Only the failure mode for an unknown record_id and the consequences of type conversion are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every one of the 16 parameters, giving a baseline of 3. The description adds one genuine cross-parameter rule, that a type change requires supplying the new type's required fields, but leaves the rest to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and scope ("Change only some fields of an existing DNS record, e.g. just data or ttl") and immediately distinguishes itself from the sibling update_dns_record. An agent can pick between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Prefer this over update_dns_record" is an explicit routing instruction, and the type-change rule ("when you change the type, give the new type's required fields too") is a real precondition. It doesn't say when NOT to use it, e.g. to create a missing record, where create_dns_record or upsert_dns_record would apply.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.