Skip to main content
Glama
Sign In
porkbun-mcp-server

porkbun-mcp-server

by Avicennasis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_dnssec_records

Retrieve DS records published for a domain to verify DNSSEC status. Returns empty if DNSSEC is not enabled.

Instructions

List the DS records Porkbun publishes for domain. Empty if DNSSEC is not enabled for the zone.

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_dnssec_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the result is empty if DNSSEC is not enabled, but it does not mention authentication requirements, rate limits, or any potential side effects. The tool appears read-only, but this is not explicitly confirmed.

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, focused sentence that conveys the core purpose and condition without unnecessary words. It is efficiently front-loaded and easy to parse.

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?

Despite lacking an output schema, the description provides key contextual information: the tool lists DS records and returns empty output if DNSSEC is not enabled. This is sufficient for a simple retrieval tool with one parameter, though it does not describe the structure of the DS records.

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?

With 0% schema description coverage, the description does not elaborate on the 'domain' parameter beyond its presence. It fails to specify format, validation, or constraints, leaving the agent to infer meaning from context.

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 (list DS records) and the resource (domain), and it specifically differentiates from related tools like 'create_dnssec_record' and 'delete_dnssec_record' by focusing on retrieval. It also notes behavior when DNSSEC is not enabled.

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 usage for checking DNSSEC status but does not explicitly state when to use this tool versus alternatives like checking DNS records or enabling DNSSEC. No exclusions or context 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