Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Pricing

get_pricing
Read-onlyIdempotent

Look up current Porkbun registration, renewal, and transfer prices by TLD in USD. Pass specific TLDs to get targeted pricing and avoid listing all available extensions.

Instructions

Get current Porkbun pricing: registration, renewal and transfer prices per TLD in USD. No authentication required. Pass tlds whenever you know which TLDs matter (e.g. ["com", "io"]): without it the response lists every TLD Porkbun sells, around 900 of them. Case, a leading dot and IDN form are handled. A TLD Porkbun does not sell comes back in unsupported instead of being priced, and if none of them are sold the call fails with INVALID_TLD. Standard pricing only: premium names have their own per-domain price, reported by check_domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldsNoTLDs to price, e.g. ["com", "io", "dev"]. Omit for every TLD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.39.4
    • addedInput schema / properties / tlds
      Added value: +{
+  "description": "TLDs to price, e.g. [\"com\", \"io\", \"dev\"]. Omit for every TLD.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 200,
+  "type": "array"
+}
  2. First observedv0.4.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description layers on genuinely non-derivable behavior: no authentication required, unsupported TLDs returned in an `unsupported` field rather than priced, and a hard INVALID_TLD failure when no requested TLD is sold. It also discloses that input normalization (case, leading dot, IDN) is handled server-side.

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?

Roughly four sentences, front-loaded with the purpose and version-free output shape, then the parameter advice, then edge-case handling. No filler; each sentence carries either routing, parameter, or error information.

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?

With no output schema, the description takes on return-shape disclosure and does it: pricing categories, currency, the `unsupported` list, and the INVALID_TLD error. Combined with annotation-covered safety and a fully documented single parameter, an agent has everything needed to call this correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value beyond the schema: acceptance of mixed case, leading dots, and IDN forms, plus why the parameter matters (response size). It does not mention the schema's 200-item cap, which is the only gap.

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?

Opens with a specific verb+resource (get Porkbun pricing) and enumerates exactly which prices are returned: registration, renewal, transfer, per TLD, in USD. It further separates itself from the closest sibling by noting premium name pricing lives in check_domain, so an agent can route correctly without opening either schema.

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?

Gives explicit when-to-use guidance ('Pass `tlds` whenever you know which TLDs matter') plus the consequence of omitting it (a ~900-entry response). It also names the alternative tool and the condition that selects it: premium names go to check_domain. Both the when and the alternative are spelled out.

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