Skip to main content
Glama

Check domain availability

check_domain
Read-only

Check if a domain is available for registration. Returns availability, premium status, and price. Supports checking a single domain (e.g. 'example.com') or a base name across multiple TLDs (e.g. domain='example', tlds=['com','de','io']).

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

Input Schema

NameRequiredDescriptionDefault
tldsNoArray of TLDs to check (e.g. ['com','de','io']). When provided, domain is treated as the base name.
domainYesFull domain (e.g. 'example.com') or base name when using tlds param (e.g. 'example')
displayNoPrice display mode (default: gross)
currencyNoCurrency for prices (default: EUR)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds value by stating what the call returns (availability, premium status, price) and that it supports multi-TLD batch-style checking, which the annotations do not convey. It stops short of describing rate limits or result ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action and its return values, followed by the two usage modes. Every sentence carries information and there is no filler.

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?

With no output schema, the description does the necessary work of naming the three return signals. It is sufficient to call the tool correctly, though it does not sketch the response structure (e.g. how per-TLD results are keyed) for the multi-TLD mode.

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 every parameter (domain, tlds, display, currency) is already documented in the schema. The description's examples restate the schema's note that domain is treated as a base name when tlds is supplied, adding consolidation but no new semantics. Baseline 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?

States a specific verb and resource ('Check if a domain is available for registration') and immediately lists the returned signals ('availability, premium status, and price'). This clearly separates it from sibling tools like get_domain, register_domain, and get_domain_pricing.

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 explains the two invocation modes precisely: a single full domain such as 'example.com', or a base name plus a tlds array such as domain='example', tlds=['com','de','io']. It does not explicitly say when to prefer this over get_domain or register_domain, so no exclusions/alternatives are given, but the usage context is clear.

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.