Skip to main content
Glama

Get DNS record

get_dns_record
Read-onlyIdempotent

Retrieve a single DNS record by its ID and domain ID, letting you inspect exact record details from Domeneshop before updating or troubleshooting DNS configuration.

Instructions

Get a single DNS record by ID.

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": "get_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_idYesthe Domeneshop domain ID, from list_domains
record_idYesthe DNS record ID, 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. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is supplied and the bar is lower. The description adds no behavioral context of its own — nothing about what happens if the record does not exist, whether lookups require elevated permissions, or any rate-limit behavior. It essentially restates the title.

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?

A single short sentence, front-loaded with the verb and resource, with no filler or redundancy. Its brevity is close to under-specification, but nothing written wastes the reader's time.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the input schema is fully annotated. What is missing is any statement about error behavior for a nonexistent record or about how this differs from the sibling list/patch/upsert DNS tools, which an agent must infer.

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%, with both domain_id and record_id documented and pointing at list_domains and list_dns_records respectively, so the baseline is 3. The description's "by ID" phrasing adds no meaning beyond the schema and is slightly imprecise about the fact that two separate identifiers are required.

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 names a specific verb and resource ("Get a single DNS record") and the singular "single" plus "by ID" distinguishes it from the plural sibling list_dns_records. It stops short of naming the sibling explicitly, so the differentiation is implied rather than stated.

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?

"by ID" implies this is the tool for fetching one known record rather than enumerating records, which is a usable hint. There is no explicit when-to-use or when-not-to-use guidance against alternatives like list_dns_records or get_domain, and no mention that both a domain ID and a record ID are prerequisites.

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