Skip to main content
Glama

Pagetool

Buy the domain for a live build (code prowess)

prowess_buy_domain

Operator token only, during a "code prowess" build the owner authorized with a spending cap. Buys ONE domain for the business through our registrar (owner-paid; no customer charge), points it at the server and starts HTTPS. Use dry_run first to compare endings. Exact business name within the cap beats a cheaper near-miss. Auto-renew stays off. Then publish_site and poll publish_status. A refused or unchecked domain ending carries reason and a plain reason_text: unsupported or price_unavailable mean we do not sell that ending right now; lookup_failed or cap_reached mean it was NOT checked, so search again, and never tell the customer we do not sell it.

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": "prowess_buy_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe ONE domain to buy for this business, bare, e.g. "heapy.net". Pick the exact business name on any ending that fits the grant's remaining cap before a cheaper misspelling (heapy.net at $90 beats heeepy.com at $40). Check prices first with dry_run.
dry_runNotrue = quote only: registrar, cost for the minimum term, and whether it fits the cap. Buys nothing.
site_keyNoThe site this domain is for (optional; for your own bookkeeping).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, open-world, non-idempotent call; the description adds what they cannot: an operator-token prerequisite, a spending cap, that the owner pays and no customer is charged, that auto-renew stays off, and that setup includes DNS pointing and HTTPS provisioning. What it omits is the most consequential behavior for a money-spending tool — whether a completed purchase can be reversed or refunded, and what state is left behind if the domain is bought but HTTPS provisioning fails.

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?

The authorization prerequisite is front-loaded and every clause carries operational weight, including the error-reason taxonomy. It is dense for a single paragraph and slightly duplicates the schema's price-versus-typo example, but the length is defensible for a tool that spends money.

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?

With no output schema, the description rightly explains the returned `reason`/`reason_text` values and how to react to each, and it covers cost, side effects, and sequencing after the call. It stops short of describing post-purchase state or failure recovery when the buy succeeds but the HTTPS/pointing step does not.

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?

Schema description coverage is 100%, so the parameters are already documented, and the description's advice to use `dry_run` first and prefer the exact business name largely restates the schema text for `domain` and `dry_run`. It adds no syntax, format, or constraint detail beyond the schema; the `reason`/`reason_text` material concerns output, not inputs.

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?

States a specific verb and resource ("Buys ONE domain for the business through our registrar") plus the follow-on effects (points it at the server, starts HTTPS). The single-domain scope and owner-paid framing are clear. It does not distinguish itself from the sibling `domain_register`, which plausibly performs a similar purchase, so an agent must infer the difference.

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 gates usage ("Operator token only, during a 'code prowess' build the owner authorized with a spending cap"), tells the agent to run `dry_run` first, states the selection rule ("Exact business name within the cap beats a cheaper near-miss"), and names the next steps (`publish_site`, poll `publish_status`). It even prescribes the recovery path for each failure reason instead of leaving the agent to guess.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources