Skip to main content
Glama

Outil.io

Buy domain

buy_domain
Destructive

Commander un domaine disponible (search_domains) pour le site du projet. ACTION FINANCIÈRE : seulement à la demande explicite du propriétaire, après avoir annoncé le domaine et le prix. Retourne checkoutUrl Stripe que le propriétaire doit ouvrir pour payer ; rien n’est enregistré avant le paiement. Le titulaire (contact) est la personne ou l’organisation propriétaire : demander ses vraies coordonnées, ne jamais les inventer. Après paiement, Outil enregistre le domaine, le raccorde au site et installe HTTPS sans réglage DNS ; suivre get_domain_order puis get_domain_status. Remplace le domaine actuellement rattaché au site.

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": {
      "hostname": "<hostname>",
      "contact": "<contact>"
    },
    "name": "buy_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYes
hostnameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so mutation and external-effect status is known. The description still adds real value beyond them: it is a financial action requiring owner consent, returns a Stripe checkoutUrl, records nothing before payment, auto-configures HTTPS without DNS, and replaces the existing domain. However, the justification lands at 3 because much of this overlaps with what the destructive/open-world annotations imply, and specific operational details—what happens to the replaced domain, whether the old one is released, how long the checkoutUrl is valid—are not stated.

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 verb and resource, then the financial-consent constraint, then the return value and workflow. Dense but every clause carries operational meaning; the semicolon-chained sentences are slightly harder to scan than a bulleted flow would be.

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?

No output schema exists, yet the description names the key return value (checkoutUrl) and explains that nothing is persisted until payment. It covers consent requirements, registrant data handling, post-payment automation, and follow-up tools—everything an agent needs to call this correctly or decide not to.

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 reported at 0%, so the description carries the burden. It clarifies that hostname must be an available domain and that contact is the legal registrant (person or organization) whose real details must be supplied, never invented—guidance the schema's field names alone do not give. It does not explain why the nested contact fields are all required or what constraints apply to country/phone beyond the schema, so it stops short of full coverage.

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?

States a specific verb and resource ('Commander un domaine disponible') and scopes it to the project site, explicitly pointing to search_domains as the availability source. It also discloses the side effect on the current domain ('Remplace le domaine actuellement rattaché au site'), which separates it from configure_domain or search_domains.

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?

Gives an explicit when-to-use gate: only on the owner's explicit request and only after announcing the domain and price. It also names the prerequisite step (search_domains) and the post-purchase follow-up tools (get_domain_order, get_domain_status), leaving no inference needed.

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.