Skip to main content
Glama

Check domain availability and indicative price

check_domain_availability
Read-onlyIdempotent

Check whether a domain can be registered and get indicative prices (first year and the yearly price after it, VAT included where it applies). Read-only: it never buys, registers or reserves a domain. alternatives:true also checks the same name on be, com, net, eu, nl, io, dev and app. Not tied to a site. The result states whether the user's plan includes buying domains in the dashboard (purchase.dashboardUrl); a domain the user already owns is connected with add_custom_domain.

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

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to check, e.g. "example.com".
alternativesNoWhen true, also check the same second-level name across a canonical TLD set (be, com, net, eu, nl, io, dev, app) and return each one's availability + indicative price.

Output Schema

NameRequiredDescriptionDefault
noteYesReminder that the price is indicative and nothing was bought.
domainYes
currencyYesISO currency code for the price (e.g. EUR).
purchaseYesWhether and where the user can buy a domain through VibeDeploy.
availableYesWhether the domain can be registered through VibeDeploy right now.
ownDomainYesHow a domain the user already owns is connected instead.
priceCentsYesIndicative first-year price in cents (VAT included where it applies), or null when no price is published.
alternativesNoPresent only when alternatives:true was requested.
renewalPriceCentsYesYearly price in cents from the second year on (VAT included where it applies), or null when no price is published. Equal to priceCents when the first year has no discount.
unavailableReasonNoSet when the registrar lists the name as free but VibeDeploy cannot register it. MULTI_YEAR_ONLY: this extension is only sold for two years or more, and VibeDeploy registers and renews one year at a time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedOutput schema / properties / alternatives / items / properties / priceCents / description
      Previous value: -"Indicative price in cents (VAT included where it applies), or null if the lookup failed."New value: +"Indicative first-year price in cents (VAT included where it applies), or null if the lookup failed."
    • addedOutput schema / properties / alternatives / items / properties / renewalPriceCents
      Added value: +{
      +  "description": "Yearly price in cents from the second year on (VAT included where it applies), or null when no price is published. Equal to priceCents when the first year has no discount.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / alternatives / items / required
      Previous value: -[
      -  "domain",
      -  "available",
      -  "priceCents",
      -  "currency"
      -]New value: +[
      +  "domain",
      +  "available",
      +  "priceCents",
      +  "renewalPriceCents",
      +  "currency"
      +]
    • changedOutput schema / properties / priceCents / description
      Previous value: -"Indicative price in cents (VAT included where it applies), or null when no price is published."New value: +"Indicative first-year price in cents (VAT included where it applies), or null when no price is published."
    • addedOutput schema / properties / renewalPriceCents
      Added value: +{
      +  "description": "Yearly price in cents from the second year on (VAT included where it applies), or null when no price is published. Equal to priceCents when the first year has no discount.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "available",
      -  "domain",
      -  "priceCents",
      -  "currency",
      -  "note",
      -  "purchase",
      -  "ownDomain"
      -]New value: +[
      +  "available",
      +  "domain",
      +  "priceCents",
      +  "renewalPriceCents",
      +  "currency",
      +  "note",
      +  "purchase",
      +  "ownDomain"
      +]
  2. Changed6 schema fields changed
    • removedOutput schema / properties / alternatives / items / properties / currency / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / alternatives / items / properties / currency / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / alternatives / items / properties / priceCents / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / alternatives / items / properties / priceCents / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / priceCents / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / priceCents / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  3. Changed6 schema fields changed
    • addedOutput schema / properties / alternatives / items / properties / unavailableReason
      Added value: +{
      +  "description": "Set when the registrar lists the name as free but VibeDeploy cannot register it. MULTI_YEAR_ONLY: this extension is only sold for two years or more, and VibeDeploy registers and renews one year at a time.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / available / description
      Previous value: -"Whether the domain can be registered right now."New value: +"Whether the domain can be registered through VibeDeploy right now."
    • addedOutput schema / properties / ownDomain
      Added value: +{
      +  "description": "How a domain the user already owns is connected instead.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / purchase
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Whether and where the user can buy a domain through VibeDeploy.",
      +  "properties": {
      +    "allowedOnPlan": {
      +      "description": "Whether the user's current plan includes buying domains through VibeDeploy.",
      +      "type": "boolean"
      +    },
      +    "dashboardUrl": {
      +      "description": "Dashboard page where the user buys domains. Buying always happens there, never through this tool.",
      +      "type": "string"
      +    },
      +    "reason": {
      +      "description": "Neutral statement of why buying is not possible. Present only when allowedOnPlan is false.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "allowedOnPlan",
      +    "dashboardUrl"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / unavailableReason
      Added value: +{
      +  "description": "Set when the registrar lists the name as free but VibeDeploy cannot register it. MULTI_YEAR_ONLY: this extension is only sold for two years or more, and VibeDeploy registers and renews one year at a time.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "available",
      -  "domain",
      -  "priceCents",
      -  "currency",
      -  "note"
      -]New value: +[
      +  "available",
      +  "domain",
      +  "priceCents",
      +  "currency",
      +  "note",
      +  "purchase",
      +  "ownDomain"
      +]
  4. Changed3 schema fields changed
    • changedOutput schema / properties / alternatives / items / properties / priceCents / description
      Previous value: -"Gross (incl. 21% VAT) indicative price in cents, or null if pricing/availability lookup failed."New value: +"Indicative price in cents (VAT included where it applies), or null if the lookup failed."
    • changedOutput schema / properties / note / description
      Previous value: -"Reminder that this is an indicative gross price and not a purchase."New value: +"Reminder that the price is indicative and nothing was bought."
    • changedOutput schema / properties / priceCents / description
      Previous value: -"Gross (incl. 21% VAT) indicative retail price in cents, or null if unavailable / no price is published."New value: +"Indicative price in cents (VAT included where it applies), or null when no price is published."
  5. Changed1 schema field changed
    • removedOutput schema / properties / request_id
      Removed value: -{
      -  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      -  "type": "string"
      -}
  6. Changed1 schema field changed
    • addedOutput schema / properties / request_id
      Added value: +{
      +  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      +  "type": "string"
      +}
  7. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the tool never buys, registers or reserves, that prices are indicative with first-year and renewal values and VAT treatment, and that the result reports plan eligibility via purchase.dashboardUrl. These are behavioral facts the annotations (readOnly/openWorld/idempotent) do not convey.

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 purpose and price semantics are front-loaded, then safety, then alternatives, then the sibling pointer — a sensible order with no filler sentences. Minor cost: the parenthetical about VAT and the fragment 'Not tied to a site' read slightly clipped.

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 two parameters, a fully documented schema, and an existing output schema, the description covers everything an agent needs: what is checked, what the price figures mean, that it is non-mutating, and where to go for existing domains.

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 baseline is 3. The description restates the alternatives:true behavior with the same TLD list already present in the schema and adds no format or syntax guidance for the domain parameter, so it does not meaningfully extend 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?

The description states a specific verb and resource ('Check whether a domain can be registered') plus a secondary outcome ('get indicative prices'), and it explicitly separates itself from add_custom_domain for already-owned domains. An agent can distinguish this from every sibling listed without opening the schema.

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?

It gives the negative case explicitly ('a domain the user already owns is connected with add_custom_domain'), states scope ('Not tied to a site'), and explains the conditional branch for alternatives:true. When-to-use and when-not-to-use are both covered.

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.