Porkbun MCP Server

get_nameservers

Get the authoritative nameservers for any domain. Provide a domain name to retrieve its current DNS nameservers, essential for domain management and troubleshooting.

Instructions

Gets the authoritative nameservers for a specified 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": "get_nameservers"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. 'Gets' clearly indicates a read-only operation, but the description does not mention return format, authentication requirements, or error scenarios. This is adequate but minimal.

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?

The description is one sentence, front-loaded with the verb and resource, and contains no filler. Every word is essential.

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 simple tool with one parameter and no output schema, the description adequately conveys the tool's purpose and implies the return value (the nameservers). It lacks explicit error handling details, but these are not critical for such a straightforward lookup.

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?

The schema covers the single parameter 'domain' with a description, and the tool description adds no new information beyond 'for a specified domain'. Since schema coverage is 100%, the baseline of 3 applies.

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 a specific action ('Gets') and resource ('authoritative nameservers for a specified domain'). This distinguishes it from sibling tools like update_nameservers (which modifies) and get_dns_records (which retrieves broader DNS records).

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?

The description implies use when you need the nameservers for a domain, but it does not explicitly mention when not to use it or provide alternative tool references. The context is clear but no exclusions or alternatives are stated.

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