instadomain

buy_domain_mpp

Start the purchase flow for a domain via Stripe's Machine Payments Protocol (MPP).

MPP lets autonomous agents pay with fiat (cards, Link) or stablecoins via Shared Payment Tokens, with no browser checkout. Two-step flow:

Step 1: Call this tool to get an order_id and pay_url. Step 2: Make an HTTP GET request to the pay_url with an MPP-enabled HTTP client. The server responds with HTTP 402 + WWW-Authenticate; the client creates a Shared Payment Token and retries with an Authorization header. The server charges the SPT through Stripe and kicks off domain registration.

After payment, call get_domain_status(order_id) to poll until complete.

Requires: An MPP-compatible client configured to mint SPTs against the server's advertised Stripe Business Network profile.

Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code. phone: Phone number in format +1.5551234567. org_name: Organization name (optional).

Returns: Dict with order_id, pay_url (full URL), price_cents, price_display, network_id, and payment_method_types.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes
`email`	Yes
`phone`	Yes
`state`	Yes
`domain`	Yes
`country`	Yes
`address1`	Yes
`org_name`	No
`last_name`	Yes
`first_name`	Yes
`postal_code`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that payment is charged via Stripe, that domain registration is kicked off, and that the client must handle HTTP 402/SPT flow. It does not mention refunds or failure modes, but given the tool is just starting a flow, the transparency is strong.

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 description is longer than average but earns its length by explaining a complex protocol. It is well-structured with separated paragraphs, a numbered two-step flow, and a clear Args/Returns breakdown. No sentence is superfluous, though it could have trimmed the exact HTTP handshake details without losing utility.

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?

Given the complexity of the MPP flow, the description is exceptionally complete: it covers prerequisites, exact step-by-step interaction, return fields, and points to the next tool (get_domain_status). The presence of an output schema also means return value details are redundant, but the description still outlines them, making it self-contained.

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 description coverage is 0%, so the description compensates by listing all parameters with some additional semantics: domain gets an example, phone gets a format, country gets '2-letter ISO', and org_name is flagged optional. Some entries like 'Registrant's first name' are slightly redundant but still add ownership context.

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?

The description clearly states 'Start the purchase flow for a domain via Stripe's Machine Payments Protocol (MPP)', which names a specific verb, resource, and protocol. It distinguishes itself from siblings like buy_domain and buy_domain_crypto by detailing the MPP-specific two-step flow and prerequisites.

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?

The description provides clear context and prerequisites: it requires an MPP-compatible client and explains the two-step flow. It also points to get_domain_status as the follow-up tool. However, it does not explicitly mention alternative tools (e.g., buy_domain_crypto) for cases where MPP is not suitable, so it falls short of a 5.

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

All instadomain tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct action or payment method. The three buy tools are clearly differentiated by payment flow (Stripe checkout, crypto x402, Stripe MPP) with explicit guidance on when to use each. All other tools have unique purposes (check, status, renew, transfer).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase snake_case (e.g., check_domain, suggest_domains, verify_transfer_code). There are no mixed conventions or ambiguous prefixes.

Tool Count5/5

With 12 tools, the set is well-scoped for a domain purchase and management service. Each tool covers a necessary step in the workflow (check, buy via 3 methods, status, renew, transfer), without unnecessary bloat.

Completeness4/5

The tool surface covers the core domain lifecycle: check availability, purchase (with multiple payment options), renew, and transfer (code request, verify, unlock). Minor gaps like listing owned domains or managing DNS are absent, but the primary use case is well-supported.

Resources

Need Help?