Skip to main content
Glama

domani

by run.domani

Buy Domain

buy_domain

Purchase one or more domains. Always confirm with the user before calling. Accepts a single domain or an array of up to 10 (card only for bulk). If the user wants to pay with crypto/USDC: call with payment_method: 'usdc' - you'll get a 402 with a wallet address and amount. Tell the user to send that amount in USDC, then once they give you the tx hash, retry with payment_tx and payment_chain. Don't explain protocol details to the user - just tell them the address, amount, and chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoNumber of years to register (1-10, default 1). Price is multiplied by years.
domainNoSingle domain to purchase, e.g. mysite.com
domainsNoArray of domains to purchase, e.g. ["a.com", "b.dev"]. Max 10.
max_priceNoCeiling in USD for the total charge. If the real price is above it, the purchase fails with PRICE_ABOVE_MAX and nothing is charged. Set it from the price the user approved.
payment_txNoTransaction hash of a USDC payment already sent on-chain. Required for step 2 of USDC flow.
payment_chainNoChain the USDC payment was sent on. Required with payment_tx.
payment_methodNoPayment method: 'card' to charge card on file, 'usdc' to pay with USDC. Overrides the user's default preference for this request.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_price
      Added value: +{
+  "description": "Ceiling in USD for the total charge. If the real price is above it, the purchase fails with PRICE_ABOVE_MAX and nothing is charged. Set it from the price the user approved.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: the 402 response with wallet address/amount, the two-step USDC flow, and the instruction to not explain protocol details. It does not mention success responses or error cases beyond PRICE_ABOVE_MAX, but the most unusual and important behaviors are well covered.

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 a single dense paragraph but every sentence contributes operational value. It front-loads the core purpose and then logically covers confirmation, bulk limits, and the USDC flow. While it is a bit long, it avoids fluff and is well organized for the complexity involved.

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?

Given 7 parameters, no output schema, and a complex payment flow, the description covers the critical contextual aspects: when to confirm, bulk constraints, USDC handling, and the 402 case. It does not describe post-purchase outcomes, but that is not essential for tool selection and invocation. The guidance is sufficient for an agent to execute the operation 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?

The schema already describes all 7 parameters with 100% coverage, so the baseline is 3. The description adds meaningful guidance beyond the schema, such as 'card only for bulk', the USDC payment flow linking payment_method, payment_tx, and payment_chain, and how max_price should be set from the user-approved price. This goes beyond mere schema repetition.

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 opens with 'Purchase one or more domains', a specific verb+resource statement. It clearly distinguishes itself from siblings by clarifying it handles purchases (not aftermarket or transfers) and supports bulk up to 10. The purpose is unambiguous and immediately knowable.

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 explicit usage instructions: always confirm with the user, use card for bulk, and a detailed USDC flow with retry steps. It does not explicitly contrast with sibling tools like acquire_domain, but it covers the main decision points for when to use this tool and how to handle alternate payment methods.

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

All domani toolsInspect
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

A3.5/5.0
Disambiguation3/5

While most tools have distinct purposes, several clusters overlap significantly (e.g., check_email, check_email_deliverability, get_email_deliverability, get_domain_email_status; buy_domain, buy_aftermarket, acquire_domain). The descriptions are detailed and help differentiate, but the sheer number of tools makes it challenging for an agent to select the correct one without careful reading.

Naming Consistency3/5

The dominant pattern is verb_noun with underscores (e.g., create_mailbox, list_domains), but there are notable inconsistencies: destructive actions mix delete/remove/cancel/revoke/unsell, and a few names deviate entirely (search, dns_check, domain_status). The pattern is recognizable but not uniformly applied.

Tool Count1/5

With 122 tools, this vastly exceeds the 50+ threshold for extreme mismatch. Even for a comprehensive domain and email platform, the tool count is overwhelming and will likely hinder agent performance through excessive choice and context bloat.

Completeness4/5

The server covers a wide range of domains, DNS, email, marketplace, negotiations, transfers, webhooks, tokens, and billing. Minor gaps exist, such as no update operation for mail rules, no direct domain deletion, and limited mailbox configuration beyond forwarding and credentials, but most lifecycle workflows are supported.

Resources