Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Diff DNS Restore Point

diff_dns_restore_point
Read-onlyIdempotent

Compare a DNS restore point against the live zone to preview records a restore would add back and identify extra live records before changing DNS.

Instructions

Compare a DNS restore point with the live zone before changing anything. Always do this before restore_dns_zone — it is free and it is the difference between fixing a zone and finding out afterwards.

missing is in the restore point but not live: these are the records a restore would ADD BACK. extra is live but not in the restore point: a restore LEAVES THESE ALONE unless you pass prune. inSync is true when both lists are empty.

Records are matched on name, type, content and priority rather than id, because an id means nothing across a delete and re-create. SOA and NS are excluded — the zone's own delegation is not what anyone means by their DNS records. For masked records (parking, ALIAS, HTTPS) the value shown is the one that was configured, not the internal host it resolves to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain, e.g. `example.com`
snapshot_idYesRestore point id from `list_dns_restore_points`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.4

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial non-obvious behavior: the meaning of missing/extra/inSync, that `extra` records survive a restore unless prune is passed, matching on name/type/content/priority rather than id, SOA/NS exclusion, and masked-record value semantics. This is rich context well beyond the annotations.

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?

Front-loads the core action and the imperative ordering before expanding into result semantics. Dense but every sentence carries distinct, useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description fully explains the return shape (missing/extra/inSync) and matching rules, which is exactly what the agent needs to interpret results. Nothing material is missing for a read-only diff tool.

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?

With 100% schema coverage and only 2 required params, the schema already documents domain and snapshot_id (including the list_dns_restore_points reference). The description adds interpretive semantics (matching rules) but no parameter syntax or format detail, so baseline 3 is appropriate.

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?

States a specific verb (compare) and resource (DNS restore point vs live zone), and explicitly distinguishes itself from restore_dns_zone as the safe pre-flight step. An agent can tell exactly what this does and why it differs from its nearest sibling.

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

Usage Guidelines5/5

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

Explicitly instructs 'Always do this before restore_dns_zone', naming the alternative and the ordering condition. It also notes it is free, giving the agent a clear when-to-use signal with no inference required.

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