Skip to main content
Glama

domain_buy

Preview a domain purchase and get a secure checkout link.

domain_buy takes project_id + domain. The platform returns the price and a dashboard_checkout_url. The price is quoted verbatim, and the secure checkout link is where payment completes.

Customer purchases cannot be completed through another MCP tool. The user completes payment through the checkout link, and registration begins only after that payment settles.

The domain is registered in the buyer's name — they own it outright and can transfer it to any registrar or account whenever they want. Mention this when sharing the checkout link; details: https://somewhere.cloud/docs/domain-ownership

Example:

{ "project_id": "my-saas", "domain": "acmedash.com" }

The response will be an error of type PURCHASE_CONFIRMATION_REQUIRED carrying the price and checkout URL, e.g. { "ok": false, "error": "PURCHASE_CONFIRMATION_REQUIRED", "domain": "acmedash.com", "price": "$17/year", "confirm_token": "...", "dashboard_checkout_url": "https://somewhere.cloud/dashboard/projects/...?tab=domains&buy=acmedash.com" }. This response is a checkout handoff: payment completes at the dashboard_checkout_url.

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": {
      "project_id": "<project_id>",
      "domain": "<domain>"
    },
    "name": "domain_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to purchase, e.g. mybooking.com
project_idYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=false and openWorldHint=true; the description goes far beyond them. It discloses the non-obvious behavior that a successful call returns an 'error' of type PURCHASE_CONFIRMATION_REQUIRED containing price, confirm_token and checkout URL, that registration begins only after payment settles, that the domain is registered in the buyer's name, and that the agent should mention ownership when sharing the link.

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 core action and the crucial behavioral caveat are front-loaded, and the worked examples earn their space since there is no output schema. It is somewhat long for two parameters, and the ownership emphasis plus docs link reads slightly like marketing copy rather than operational guidance.

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 carries full responsibility for the return shape, and it delivers a concrete response example including the confirm_token and dashboard_checkout_url. For a two-parameter purchase-handoff tool, an agent has everything needed to call it and to interpret the result correctly.

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 both parameters are already documented, which sets the baseline at 3. The description contributes a worked example pairing project_id and domain and reinforces the verbatim-price behavior, but adds no format, constraint, or validation detail beyond the schema.

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 statement: 'Preview a domain purchase and get a secure checkout link,' and immediately names the two inputs it takes. It also distinguishes itself from the rest of the toolset by stating that customer purchases cannot be completed through another MCP tool, so an agent knows this is the only purchase path rather than a check or list operation.

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?

It clearly frames the use case: call this to get a price and a checkout handoff, then the human pays at the link. It also gives an exclusion ('cannot be completed through another MCP tool'), but it never tells the agent to run a domain availability check first, nor does it name domain_check or domain_list as prerequisites or alternatives.

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