Skip to main content
Glama

Read DNS records

domainRecords
Read-onlyIdempotent

Read the DNS records of one domain Tofu registered for this account — Your domains → DNS records on the dashboard’s Domains page. In records, host is relative to the domain (empty is the domain itself). managedBy: "tofu" marks a record Tofu keeps for the site — its routing, the ownership proof, the padlock’s validation — and purpose says which protected site-management purpose it serves. Each record’s deletable says whether THIS caller may delete it, and note says why not. editable: false means no record can be added or deleted right now, and message says why. zoneFile: true also returns the records as a standard zone file, to rebuild the DNS at another host; complete: false means records and zoneFile hold only part of the zone. A domain this account did not register through Tofu answers as not found: its DNS is wherever the owner keeps it, and domainGuidance reads that for a connected hostname. This tool changes nothing.

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": "<domain>"
    },
    "name": "domainRecords"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
zoneFileNo

Output Schema

NameRequiredDescriptionDefault
domainYes
messageYes
recordsYes
completeYes
editableYes
zoneFileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, closed-world call, and the description reinforces this with 'This tool changes nothing.' It adds behavior the annotations cannot carry: how not-found results arise for non-Tofu domains, the meaning of editable:false plus a reason message, and that complete:false means both records and zoneFile are partial.

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?

The identifying statement leads, followed by field-level clarifications that each carry distinct information. It is a single dense paragraph, though, with many backticked field references that make it a bit heavy to scan.

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

Completeness5/5

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

Even with an output schema present, the description supplies the interpretive layer an agent needs: which records are Tofu-managed, why a record may be undeletable, why editing may be blocked, and how partial zones surface. Nothing required to call it correctly is missing.

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

Parameters4/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, and it does: zoneFile:true is explained as returning a standard zone file for rebuilding DNS elsewhere, and domain is implicitly scoped to Tofu-registered domains. The domain parameter's naming and pattern constraints are left to the schema, which costs only a little.

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 resource ('Read the DNS records of one domain Tofu registered for this account') and scopes it to Tofu-registered domains, which cleanly separates it from domainRecordAdd, domainRecordDelete and domainGuidance.

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?

Gives a clear precondition (the domain must be registered through Tofu) and explicitly routes the out-of-scope case to domainGuidance for connected hostnames. It stops short of mentioning record-mutation siblings such as domainRecordAdd or domainRecordDelete as the path when editing is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources