Skip to main content
Glama

check_domain_availability

Read-only

Check whether domain names can be registered through AIvikings. Takes a list of one or more names (up to 200). Each result has a status: available (confirmed free by the registry), probably_available (not registered as far as we can see, but NOT confirmed: lists of more than 50 names are not sent to the registry; check the shortlist again to confirm), taken, not_offered (AIvikings does not sell that TLD), invalid (see message), or try_again (could not be confirmed right now). Never tell the user a probably_available name is available. This tool does not return prices or premium status: before the user buys, always call get_domain_pricing for the chosen name and tell them if it is premium. For a single name or a short list (up to 10), include_price=true adds premium and prices in the same call.

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": {
      "domains": "<domains>"
    },
    "name": "check_domain_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes
currencyNoUSD
include_priceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / depth
      Removed value: -{
      -  "default": "confirm",
      -  "title": "Depth",
      -  "type": "string"
      -}
    • addedInput schema / properties / include_price
      Added value: +{
      +  "default": false,
      +  "title": "Include Price",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Beyond readOnly/openWorld annotations, it discloses the key behavioral quirk that lists over 50 names are never sent to the registry (producing probably_available), and that prices/premium status are out of scope. It does not discuss rate limits or response payload beyond the status enumeration, so it is strong but not exhaustive for an open-world network tool.

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-loads purpose, then the status taxonomy, then the escalation rule to pricing, then the include_price shortcut. Dense but every sentence carries operational meaning; the nested parenthetical about the 50-name registry cutoff is slightly awkward but worth keeping.

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?

Given an output schema exists, return values need not be explained, yet the status enumeration is still offered as decision-relevant guidance. The only real gap is the undocumented currency parameter and no note on how domain strings are normalized or validated.

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 0%, so the description must carry parameter meaning. It explains domains (one or more, up to 200) and the crucial caveat that include_price only applies to short lists, but the currency parameter is never mentioned and no format examples are given for domain strings.

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 whether domain names can be registered through AIvikings') and explicitly contrasts itself with get_domain_pricing for pricing. An agent can distinguish it from list_domains or register_domain without opening any 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 concrete routing guidance: call get_domain_pricing before the user buys, use include_price=true only for a single name or lists up to 10, and never report probably_available as available. It also sets a hard upper bound of 200 names, so the agent knows the operating envelope.

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.