vibedeploy

Check domain availability and indicative price

check_domain_availability

Read-onlyIdempotent

Check whether a domain can be registered and get an INDICATIVE retail price. IMPORTANT: this is a read-only lookup — it does NOT buy, register, reserve, or pay for any domain, and it changes nothing. The returned price is GROSS (includes 21% VAT) and indicative only. Set alternatives:true to also check the same name across other common TLDs (be, com, net, eu, nl, io, dev, app). Requires a valid team token but is not tied to a specific site.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	The domain to check, e.g. "example.com".
`alternatives`	No	When 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

TableJSON Schema

Name	Required	Description
`note`	Yes	Reminder that this is an indicative gross price and not a purchase.
`domain`	Yes
`currency`	Yes	ISO currency code for the price (e.g. EUR).
`available`	Yes	Whether the domain can be registered right now.
`priceCents`	Yes	Gross (incl. 21% VAT) indicative retail price in cents, or null if unavailable / no price is published.
`alternatives`	No	Present only when alternatives:true was requested.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

removedOutput schema / properties / request_id

Removed value: -{
-  "description": "Server-assigned request correlation id. Quote it when contacting support.",
-  "type": "string"
-}

Changed1 schema field changedJul 20, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "Server-assigned request correlation id. Quote it when contacting support.",
+  "type": "string"
+}

First observedJun 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Even though annotations already mark this as read-only, idempotent, and non-destructive, the description adds meaningful behavioral detail: it never purchases or registers, returns gross prices including 21% VAT, prices are indicative only, and the call is not site-scoped. This goes well beyond the annotation hints.

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 well-structured and front-loaded with the core purpose and read-only warning. It is slightly longer than necessary because the alternatives sentence largely duplicates the schema description, but every included detail serves a purpose such as VAT, TLDs, and token requirements.

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?

The tool is simple, has fully documented parameters, an output schema, and strong annotations. The description covers purpose, read-only safety, pricing semantics, TLD behavior, authentication, and site-scoping, leaving no significant gap for correct invocation.

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%: both domain and alternatives are already fully documented in the input schema. The description restates the alternatives behavior and the TLD set but does not add significant new parameter meaning beyond what the schema provides, so the baseline score of 3 applies.

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 a specific verb and resource: 'Check whether a domain can be registered and get an INDICATIVE retail price.' It clearly distinguishes this from site-related sibling tools like add_custom_domain by noting it is not tied to a specific site and does not buy or register 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?

The description gives explicit when-to-use and when-not-to-use guidance: it is a read-only lookup and 'does NOT buy, register, reserve, or pay for any domain.' It also adds practical context by stating a valid team token is required and that it is not tied to a specific site, plus guidance for the alternatives parameter.

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

All vibedeploy tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.