Skip to main content
Glama
Sign In
AgentDomain

AgentDomain

by MarsHeer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

domain_dns_get

Retrieve all DNS records for a domain including A, CNAME, MX, and TXT records.

Instructions

Get DNS records for a domain.

Returns all DNS records (A, CNAME, MX, TXT, etc.) for the domain.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Returns all DNS records' but does not disclose behavior for missing domains, authentication requirements, rate limits, or any side effects. The read-only nature is implied but not explicit.

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?

Two short sentences with no fluff. The second sentence partially repeats the first by enumerating record types, but it's not excessive. Could be merged into one concise sentence without loss.

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?

Given only one parameter and presence of an output schema, the description is minimally sufficient. However, it lacks information about error cases, permissions, or behavior when domain is invalid. With no annotations, more context is needed for a higher score.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for the only parameter 'domain'. The description adds no additional semantics beyond 'for a domain'—no format, example, or constraints. It fails to compensate for the schema gap.

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 clearly states the action (Get DNS records) and the resource (domain). It lists specific record types (A, CNAME, MX, TXT), distinguishing it from sibling tools like domain_dns_update which modifies records.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention that this is for reading records, nor does it specify when to use domain_dns_update or other siblings. No prerequisites or exclusions are provided.

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