Skip to main content
Glama
agentisend

agentisend

Get domain

get_domain
Read-onlyIdempotent

Read a domain's last-checked DNS record status, including required and observed values, TTL, priority, TLS mode, and recent events; run verification to perform a new check.

Instructions

Purpose: read one domain and see which of its DNS records are in place. NOT for: re-checking DNS — this returns the last check; verify_domain runs a new one. Returns: the same domain view GET /domains/:id returns, including tls_mode, every record with its status, host, value_strings, TTL, priority, required and observed, plus recent_events (the five newest timeline rows; the full list is GET /domains/:id/events). Pass the domain id or the domain name as domain_id. id and name mean the same thing.

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

Input Schema

NameRequiredDescriptionDefault
domain_idYesThe domain id or the domain name. name is an alias for this argument.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
nameNo
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
regionNo
statusNopending, verified, failed or temporary_failure.
recordsNoEach DNS record with its status.
tls_modeNoopportunistic or enforced.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses a critical behavioral trait: the record statuses are a cached snapshot from the last check, not live, and it caps recent_events at the five newest rows while pointing to the full-events endpoint. These are exactly the kind of staleness/scope limits an agent needs.

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?

Purpose / NOT-for / Returns structure is front-loaded and easy to parse. The Returns paragraph is somewhat long given an output schema already exists, so it isn't maximally tight, but every line still earns its place.

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?

For a single-parameter read tool with a rich output schema and full annotations, the description covers purpose, exclusions, the alternative sibling, and the staleness caveat. Nothing needed to select or invoke it correctly is missing.

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 coverage is already 100% and the schema itself documents that 'name is an alias for this argument,' so the description's restatement that 'id and name mean the same thing' is largely redundant. Baseline 3 applies when the schema carries the parameter semantics.

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 opens with a specific verb and resource: 'read one domain and see which of its DNS records are in place.' This distinguishes it from list_domains (plural listing) and from verify_domain/wait_for_domain, which perform new checks.

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 explicitly states when-not and names the alternative: 'NOT for: re-checking DNS — this returns the last check; verify_domain runs a new one.' That is a direct routing rule an agent can act on without opening any schema.

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