Skip to main content
Glama
Sign In
DNS Doctor

DNS Doctor

by dnsdoctor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Get Domain Setup Records

get_domain_records
Read-onlyIdempotent

Retrieve read-only DNS records a monitored domain still needs: the ownership check while unverified, or the DMARC reporting record and observed publication status once verified.

Instructions

Read the records a domain the user monitors still needs: the ownership check while it is unverified, and once verified the DMARC reporting record plus whether we have OBSERVED that record published. Read-only: it issues nothing — if a verified domain comes back with no reporting record yet, call check_domain_verification once, which issues it. Print every record host and value EXACTLY as returned — never rewrite, reformat or improve a record string. Nothing here is applied to anyone's DNS: a human publishes every record, and you must show them what you are about to add and get their approval before using any DNS tool of your own. When guidance.note is present, relay it as given: it covers edge cases such as a domain on Automatic DMARC.

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain, e.g. example.com. For add_monitored_domain: any registrable domain the linked account owns (re-adding one it already monitors returns that row). For check_domain_verification and get_domain_records: a domain this account already monitors, verified or still pending. Any other name — another account's, or one nobody monitors — is refused as not found; ownership is never disclosed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.1
    • changedInput schema / properties / domain / description
      Previous value: -"One of the token account's VERIFIED monitored domains, e.g. example.com. Any other name — another account's, or one nobody monitors — is refused as not found; ownership is never disclosed."New value: +"The domain, e.g. example.com. For add_monitored_domain: any registrable domain the linked account owns (re-adding one it already monitors returns that row). For check_domain_verification and get_domain_records: a domain this account already monitors, verified or still pending. Any other name — another account's, or one nobody monitors — is refused as not found; ownership is never disclosed."
  2. Addedv1.9.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description adds non-obvious behavior: nothing here is applied to DNS, a human must publish, record strings must be printed verbatim, and guidance.note should be relayed as given. It also discloses the observed-vs-published distinction in the returned data, which annotations cannot express.

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 return content is front-loaded and each sentence carries operational instruction rather than filler. It is dense with rules (verbatim printing, approval gate, note relay), which is justified but makes it longer than strictly minimal.

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?

With no output schema, the description does describe the returned artifacts (record host/value, observed-publication flag, guidance.note) and the not-issuing semantics. It stops short of describing error/not-found responses or the exact response envelope, leaving a small gap for a no-output-schema tool.

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 100% and the single domain parameter is fully documented in the schema, including the not-found/ownership-disclosure behavior. The description adds no parameter-level syntax or format detail, so it sits at the baseline where the schema does the work.

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?

The description names the concrete resources returned (ownership check record while unverified, DMARC reporting record plus observed-publication status once verified) with a specific verb, so the agent knows exactly what it yields. It also implicitly separates this from check_domain_verification by saying that sibling 'issues' the record while this one 'issues nothing'.

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

Usage Guidelines5/5

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

It gives an explicit branch instruction: if a verified domain comes back with no reporting record, call check_domain_verification once. It also sets a clear boundary for downstream actions — show the human and get approval before using any DNS tool of your own.

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