Skip to main content
Glama
hofill
by hofill

update_dns

Replace all DNS records for domains with new configurations including A, AAAA, CNAME, and TXT records. Confirm changes to update DNS settings.

Instructions

Replace the full DNS records set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordsYes
confirmYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The RequestrepoMCPService.update_dns method implements the core business logic for the update_dns tool. It validates confirmation, converts input records to DnsRecord models, calls the client to update DNS, and returns the updated records count and details.
    def update_dns(self, *, records: list[DnsRecordInput], confirm: bool) -> dict[str, Any]:
        self._require_confirm(confirm, "update_dns")
        dns_records = [DnsRecord(type=record.type, domain=record.domain, value=record.value) for record in records]
        updated = self._client().update_dns(dns_records)
        return {
            "updated": updated,
            "count": len(dns_records),
            "records": [serialize_dns_record(record) for record in dns_records],
        }
  • The MCP tool registration for update_dns. This @mcp.tool() decorated function exposes the update_dns operation to the MCP server, accepting a list of DnsRecordInput and a confirm boolean parameter.
    @mcp.tool()
    def update_dns(records: list[DnsRecordInput], confirm: bool) -> dict[str, Any]:
        """Replace the full DNS records set."""
        return resolved_service.update_dns(records=records, confirm=confirm)
  • Schema definitions for update_dns tool inputs. DnsRecordType defines allowed DNS record types (A, AAAA, CNAME, TXT) and DnsRecordInput is the Pydantic BaseModel used for each DNS record in the update_dns tool.
    DnsRecordType = Literal["A", "AAAA", "CNAME", "TXT"]
    
    
    class DnsRecordInput(BaseModel):
        """DNS record payload for update_dns."""
    
        type: DnsRecordType
        domain: str
        value: str
  • Helper function serialize_dns_record that converts DnsRecord objects to dictionaries for API responses. Used by the update_dns handler to format output records.
    def serialize_dns_record(record: DnsRecord) -> dict[str, str]:
        return {
            "type": record.type,
            "domain": record.domain,
            "value": record.value,
        }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Replace the full DNS records set' implies a destructive mutation operation, but it doesn't disclose critical behaviors: whether this requires admin permissions, if changes are immediate or propagate slowly, what happens to existing records not included, or if there are rate limits. The description is minimal and lacks necessary operational context.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place in conveying the tool's purpose.

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?

Given this is a destructive mutation tool with no annotations, 0% schema description coverage, but with an output schema, the description is inadequate. It doesn't address safety concerns, permission requirements, or operational implications of replacing DNS records. The presence of an output schema helps with return values, but the description should do more to contextualize this high-impact operation.

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 description coverage is 0%, so the description must compensate. It mentions 'full DNS records set' which hints at the 'records' parameter being an array of records, but doesn't explain the 'confirm' parameter or provide details about record structure (type, domain, value). The description adds some context but doesn't fully compensate for the schema's lack of descriptions.

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

Purpose4/5

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

The description 'Replace the full DNS records set' clearly states the action (replace) and resource (DNS records set). It's specific about replacing the entire set rather than partial updates, which distinguishes it from potential sibling tools like 'add_dns' or 'remove_dns'. However, it doesn't explicitly differentiate from all siblings like 'update_files'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'add_dns', 'remove_dns', or 'list_dns', nor does it specify prerequisites, consequences, or appropriate contexts for replacing DNS records versus other operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hofill/RequestRepo-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server