Skip to main content
Glama

Is a domain name available?

domain_availability
Read-only

registered, available or unknown, from the registry RDAP and a DNS delegation check. A read that failed answers unknown, and unknown is not charged. Needs a DomainDrift API key.

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

Input Schema

NameRequiredDescriptionDefault
domainYesRegistrable domain name, e.g. "example.com"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value by disclosing the data sources, the failure-to-unknown behavior, and that unknown results are free. It still omits the cost of charged lookups, latency/rate limits, and what an invalid or non-registrable domain yields. Useful added context, but not a full behavioral picture.

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?

Two tight sentences with no filler, and the outcome vocabulary is front-loaded. The cost is that the leading fragment lacks a subject, making the first clause read as if a word was dropped.

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?

For a one-parameter read-only check with no output schema, the description covers the result space (three verdicts), the evidence behind them, failure semantics, billing, and auth. Remaining gaps are secondary operational details like charged-call pricing and input validation rules.

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?

Only one parameter with 100% schema description coverage including an example, so the schema does the work and the baseline is 3. The description adds nothing about the domain argument (e.g. IDN handling, subdomain rejection) beyond what the schema already states.

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?

Names the three possible verdicts (registered, available, unknown) and the two evidence sources (registry RDAP plus a DNS delegation check), which is specific enough to separate it from generic whois/lookup siblings. The opening is a sentence fragment that leans on the title for its verb ('Is a domain name available?'), so the purpose is clear but not self-contained.

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?

No statement of when to prefer this over siblings such as lookup_domain or whois_lookup, and no exclusions or prerequisites beyond the API key. The only guidance-adjacent content is the billing note that unknown answers are not charged, which informs cost, not tool selection.

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