Skip to main content
Glama
Sign In
porkbun-mcp

porkbun-mcp

by major
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

domains_create_glue_record

Create glue records for self-hosted nameservers by specifying domain, subdomain, and IPs. Essential for delegating DNS to custom nameservers.

Instructions

Create a glue record for self-hosted nameservers.

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>",
      "subdomain": "<subdomain>",
      "ips": "<ips>"
    },
    "name": "domains_create_glue_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipsYesList of IP addresses (IPv4 and/or IPv6)
domainYesDomain name (e.g., 'example.com')
subdomainYesSubdomain for the nameserver (e.g., 'ns1')

Output Schema

NameRequiredDescriptionDefault
statusYesOperation status
messageYesConfirmation message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.7/5.0
Behavior2/5

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

The description only repeats the operation type (create) without disclosing any behavioral details such as duplicate handling, permissions, prerequisites, or side effects. The annotation idempotentHint=false provides minimal context, but the description adds no extra transparency beyond what is already obvious from the verb.

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 a single, short sentence that is front-loaded with the core action. It is efficient and contains no unnecessary words or verbose details.

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?

The description is minimally sufficient for a simple create operation, especially with a complete schema and output schema present. However, it does not explain any edge cases, failure conditions, or the significance of a glue record beyond the basic purpose, leaving some context gaps.

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 input schema describes all parameters (domain, subdomain, ips) with examples and type information, so schema coverage is 100%. The description itself adds no parameter-specific value, but the baseline of 3 is appropriate given the schema's completeness.

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 (Create) and the resource (glue record for self-hosted nameservers), making it specific and easy to distinguish from sibling tools like domains_update_glue_record or domains_delete_glue_record. This is a precise verb+resource pairing.

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?

The purpose implies that this tool is used when creating a new glue record, which is a clear context. However, it does not explicitly mention when not to use it or name alternative tools, so it lacks exclusions. The distinction from other glue-record tools is implied but not stated.

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