Skip to main content
Glama

domains_create

Register a Porkbun domain with a cost quote, dry-run by default, and explicit confirmations before purchase. Card payment uses an idempotency key; the payment link is not paid.

Instructions

Register a domain. cost is integer US cents matching the current quote. dry_run defaults to true and makes no API call; execution requires dry_run=false, confirm_apply=true, agree_to_terms=true, write mode and domain-create enablement. Card execution requires a saved caller-generated idempotency_key. Reuse it only for identical retries; use a new key when adding card_payment_id. This tool never pays the link.

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>",
      "cost": "<cost>"
    },
    "name": "domains_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
domainYes
dry_runNo
pay_withNo
confirm_applyNo
agree_to_termsNo
card_payment_idNo
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • addedInput schema / properties / card_payment_id
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,255}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / cost / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{16,128}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / pay_with
      Added value: +{
      +  "const": "card",
      +  "type": "string"
      +}
  2. First observedv0.3.6

TDQS

A4.4/5.0
Behavior5/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 and does so well: it discloses the dry-run default and its no-op nature, the multi-flag execution gate, the write-mode/enablement dependency, and the idempotency replay rules. The closing note that it "never pays the link" sets an important scope boundary for a payment-adjacent mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then layers cost, dry-run default, execution gate, idempotency and scope in rough order of importance. Dense semicolon chaining makes it slightly telegraphic, but almost every clause carries operational information.

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 an 8-parameter, no-annotation, no-output-schema mutation involving payment, the description covers safety gating, idempotency and cost semantics thoroughly. It leaves implicit what a successful registration returns and whether availability must be checked first, which keeps it just short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely does: cost is defined as integer US cents tied to the quote, dry_run's default is given, and idempotency_key's caller-generated nature plus reuse rules (new key when adding card_payment_id) add meaning the schema's regex cannot convey. confirm_apply, agree_to_terms and card_payment_id are covered via the execution-gate and card sentences.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: "Register a domain." That is clearly distinct from siblings like domains_check_availability, domains_update_auto_renew or the dns_* tools, though the description never names those alternatives explicitly.

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?

States that cost must match the current quote, that dry_run defaults to true and makes no API call, and enumerates the exact conditions for execution (dry_run=false, confirm_apply=true, agree_to_terms=true, write mode, domain-create enablement). It does not point to domains_check_availability or pricing_get as prerequisite steps, which is the main gap.

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