Skip to main content
Glama

Read DNS guidance

domainGuidance
Read-onlyIdempotent

Read the DNS picture behind ONE connected hostname — the Domains page’s provider guidance. It takes a connection’s domainId, never a hostname; another project’s connection answers exactly as the dashboard does. lookup: not_read (reason: routing_unconfirmed) means Tofu has not queried public DNS because the routing setting is unconfirmed: its message explains that unobserved state, with no conclusion about missing records or propagation. Otherwise it reports the nameservers a fixed public resolver returned, their provider’s ordered steps, the reported pitfalls and conflicts (records that would fight the one Tofu asks for). root.support: no means this app cannot use a domain’s root on any DNS host; root.www connects instead, with the root forwarding to it at the domain registrar. It is what Tofu saw, the page’s own read, not a diagnosis. It writes no DNS and returns no credential.

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": {
      "projectId": "<projectId>",
      "domainId": "<domainId>"
    },
    "name": "domainGuidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
rootNo
zoneNo
stepsNo
lookupYes
reasonNo
messageYes
existingNo
hostnameYes
pitfallsNo
providerNo
resolverNo
checkedAtNo
conflictsNo
cnameTargetNo
nameserversNo
domainConnectNo
providerLabelNo
negativeCacheMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes beyond them: it discloses that `lookup: not_read` means public DNS was never queried and carries no conclusion about missing records or propagation, that nameservers come from a fixed public resolver, and that it writes no DNS and returns no credentials. Some of this overlaps the output schema's enumerated fields, but the interpretation of those states is genuinely added context.

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

Conciseness3/5

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

Purpose is front-loaded in the opening clause, which is good, but the body is a dense run of backticked tokens and nested clauses that is hard to parse at a glance. The sentence 'another project's connection answers exactly as the dashboard does' is ambiguous and does not clearly earn its place.

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 read-only, two-UUID tool with an output schema, the description covers what is missing elsewhere: the domainId-vs-hostname rule, the meaning of the not_read/lookup state, and the root.support/root.www implication. Only the `projectId` parameter and the choice among sibling domain tools are left unexplained.

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?

With 0% schema description coverage, the description must carry parameter meaning. It does for `domainId` — 'a connection's `domainId`, never a hostname' is exactly the disambiguation an agent needs — but `projectId` is never mentioned, leaving half the required inputs to the bare UUID pattern.

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 first sentence names a specific verb and resource: 'Read the DNS picture behind ONE connected hostname — the Domains page's provider guidance.' It also fixes scope ('ONE', tied to a connection) and contrasts with a hostname-based lookup. It never names a sibling tool, so an agent must infer from names alone which of domains/domainVerify/domainRecords to choose instead.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'It is what Tofu saw, the page's own read, not a diagnosis' hints this is informational and that a diagnosis would come elsewhere, and 'another project's connection answers exactly as the dashboard does' hints the guidance is provider-level. There is no explicit when-to-use/when-not or named alternative, so routing between this and the verification siblings remains an inference.

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