Skip to main content
Glama

Check domains

check_domains
Read-onlyIdempotent

Checks whether specific domain names are free to register, for exact domains such as brightfield.com or brightfield.io. Up to 50 a call. Each result has domain, available (true, false or null), status (available, taken or unknown), checked_at, confirmed and by (registry, registrar, dns, dns_only or confirming); confirmed=false means the answer came from DNS and is still being confirmed. A free domain has price (first_year, renews, min_years, currency USD) and buy_url, a link to register that domain at a registrar. A taken domain has registrar, registered and expires when the registry publishes them. For the first 3 taken domains, alternatives lists up to 3 domains with the same name on other endings that were free when checked, each with price and buy_url.

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

Input Schema

NameRequiredDescriptionDefault
domainsYesFull domain names, such as ["brightfield.com", "brightfield.co.uk"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description earns credit for adding real semantics: the meaning of available=null/unknown, the fact that confirmed=false means a DNS-only provisional answer, and that registrar/registered/expires are only present when the registry publishes them. It does not cover latency, caching, or quota cost, which is the remaining gap.

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?

Purpose and scope are front-loaded in the first sentence, then return semantics follow in a logical order. It is dense but each sentence carries information; the paired 'available (true, false or null), status (available, taken or unknown)' enumeration is mildly redundant but resolves the null case.

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 must carry the return contract, and it does so thoroughly — result fields, the confirmation lifecycle, price/buy_url, and the alternatives block for the first 3 taken domains. It leaves out error behavior for malformed or unsupported TLDs and any indication of whether results are live or cached.

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% for the single 'domains' parameter, which already documents full domain names with an example. The description only restates the call-size limit (matching maxItems=50) and the exact-name requirement, adding little beyond the schema. 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 ('Checks whether specific domain names are free to register') and narrows scope to 'exact domains such as brightfield.com', which implicitly separates it from the name-search and suggestion siblings. An agent can tell it is a registrability lookup, not a search.

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

Usage Guidelines3/5

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

The 'exact domains' framing and the 'Up to 50 a call' limit give implied usage context, so an agent can infer this is for known-name availability checks rather than discovery. However, it never explicitly says when to use this versus search_name, suggest_names, or domain_details, and states no alternatives or exclusions.

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