Skip to main content
Glama

Check domain availability (RDAP)

check_domain_availability
Read-onlyIdempotent

Check whether domain names are free or registered using official RDAP. Pass full domains, or brand names plus TLDs. Returns available or registered, registrar, expiry date, age and nameservers. Max 12 domains per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_domain_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldsNoTLDs to combine with names (default com, io, ai, dev).
namesNoBrand names without TLD, e.g. "mybrand".
detailsNoInclude registrar, dates and nameservers (default true).
domainsNoFull domains, e.g. "example.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds real value beyond that by naming the returned fields (availability, registrar, expiry, age, nameservers) and the 12-domain cap per call. It does not explain rate limits, failure behavior for unsupported TLDs, or what happens when RDAP lookup misses.

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 short sentences, front-loaded with the verb and mechanism, then input modes, then return shape, then the batching limit. No filler or repetition.

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?

For a read-only lookup tool with no output schema, the description covers purpose, both input modes, the returned fields and the per-call cap — everything an agent needs to call it correctly and interpret the result.

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 coverage is 100%, so every parameter already carries its own description including defaults and maxItems. The description's 'full domains, or brand names plus TLDs' restates the domains-versus-names/tlds split that the schema already documents, adding little new meaning. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — check whether domains are free or registered — and names the data source (official RDAP). The purpose is unambiguous and inherently distinct from the sibling check_domain_health, though it never explicitly contrasts itself with any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the two input modes (full domains, or names plus TLDs) but gives no when-to-use framing, no prerequisites, and no conditions under which another tool (e.g. check_domain_health) should be preferred. Usage context is left entirely to inference.

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.

Resources