Impreza Host MCP Server

Overview Schema Source Related Servers Discussions Admin

impreza_list_dns

List DNS records (host, type, value, TTL, priority) for a domain on Impreza-managed DNS. Read-only retrieval of DNS configuration.

Instructions

List the DNS records (host, type, value, TTL, priority) for a domain on Impreza-managed DNS. Read-only.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The description labels the tool as 'Read-only,' which is good given no annotations, but lacks details on authentication, behavior for non-existent domains, or rate limits.

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

Conciseness5/5

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

A single sentence, no wasted words; front-loaded with the action and key information.

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?

Adequate for a simple list tool with one parameter and no output schema. Could mention potential errors or pagination, but not essential.

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

Parameters4/5

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

The schema already describes the 'domain' parameter. The description adds value by enumerating the returned fields (host, type, value, TTL, priority).

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 tool lists DNS records (with specific fields) for a domain, which is distinct from sibling tools like impreza_add_dns_record or impreza_delete_dns_record.

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

Usage Guidelines4/5

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

It implies this is the read-only alternative to add/delete/update DNS records, but does not explicitly state when to use or provide exclusions. The context from sibling names helps.

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