Skip to main content
Glama

Domain Availability Check

available
Read-onlyIdempotent

Confirm a single domain's registrability and price. The definitive availability check for one domain. For two or more domains call bulk_available once instead of repeating this tool. Concurrent calls are not supported: send one call, wait for its result, then send the next; parallel calls are rejected and return no data.

Related: bulk_available, whois, monitor.

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

Input Schema

NameRequiredDescriptionDefault
domainYesFull domain with TLD (e.g., 'example.com')

Output Schema

NameRequiredDescriptionDefault
priceNoRegistration price with currency (e.g., '9.99 USD'). Only present when status=available.
domainNo
statusNoDomain status: available = registrable, registered = taken, expiring = in the expiration pipeline, reserved = registry-reserved, invalid = malformed input, unknown = inconclusive
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success",
      -  "domain",
      -  "status"
      -]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds a non-obvious operational trait the annotations do not encode: concurrent/parallel calls are rejected and return no data, so calls must be serialized. That is exactly the kind of context that prevents silent empty results from an agent fanning out requests.

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?

Front-loaded with the core purpose, then routing rule, then operational constraint, then related tools — a logical order with no wasted preamble. The second sentence ("the definitive availability check for one domain") partially restates the first, a minor redundancy given the otherwise tight construction.

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 one-parameter tool with annotations and an output schema, the description covers purpose, when to use a sibling instead, a concurrency pitfall, and related tools. Nothing an agent needs in order to call it correctly and interpret the absence of data is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is fully documented in the schema (100% coverage) with a format example, so the baseline is already high. The description reinforces that the tool takes exactly one domain rather than a list, which adds modest meaning beyond the schema but does not specify anything the schema omits.

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?

"Confirm a single domain's registrability and price" names a specific verb (confirm) and resource (domain registrability/price), and "the definitive availability check for one domain" scopes it to exactly one domain. This directly separates it from the bulk_available sibling, so an agent can route without opening either 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?

Gives an explicit alternative and the condition that selects it: "For two or more domains call bulk_available once instead of repeating this tool." It also names related tools (whois, monitor) and adds a hard usage constraint about serialized calls, leaving nothing 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.