Skip to main content
Glama

Check whether domain names are available to register (live registry lookup)

stake_check_domains
Read-onlyIdempotent

Use when the user asks whether a domain is available or taken, wants product, startup, app or project name ideas with a free domain, or is about to put a domain into a plan, README, config or launch post (signals: "is the .com taken", "domain available", "name ideas with a .com", "which of these names has a free domain", ".io or .ai", "who owns this domain", "when does it expire"). Asks each ending's own registry through RDAP (the official successor to WHOIS; IANA's server list plus the registries of .io, .me, .sh, .ac, .us, .so, .de, .ch that are not in it), and returns per domain: available, registered, registered_expiring (redemption or pending delete), likely_available (DNS only: for endings with no public RDAP such as .co, .gg, .eu, .it, or when a registry's RDAP server refuses or rate-limits the check), unknown or invalid; for taken names the registration and expiry dates, days to expiry, registrar, status codes and nameservers, and a flag when the nameservers belong to a parking or domain-marketplace service (Afternic, Dan.com, Sedo, Atom and others: the owner may sell it). Pass full domains, or names plus endings: {"names":["tidewell","brightloop"],"tlds":["com","io","ai"]} or {"domains":["tidewell.com","münchen.de","foo.co.uk"]}. Default endings when only names are given: com, io, ai, dev, app, co, net, org. Up to 20 domains per call. Call it before presenting name ideas as available instead of guessing. Cannot see prices, premium or reserved status, trademarks, or social handles; "available" is not a reservation.

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

Input Schema

NameRequiredDescriptionDefault
tldsNoEndings to try with names, e.g. ["com","io","ai","dev"] (a leading dot is fine; co.uk works). Default: com, io, ai, dev, app, co, net, org.
namesNoBare names without an ending, e.g. ["tidewell"]; each is checked with every entry in tlds. Up to 10 names (and 20 domains in total).
domainsNoFull domain names to check, e.g. ["tidewell.com", "tidewell.io"]. International names (münchen.de) and suffixes such as co.uk are fine; a URL or subdomain is reduced to the registrable domain. Up to 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses the lookup chain (IANA server list plus specific registries not in it), the DNS-only fallback for TLDs without public RDAP or when a registry refuses or rate-limits, and the parking/marketplace nameserver flag (Afternic, Dan.com, Sedo, Atom). It also warns that "available" is not a reservation and that 20 domains per call is the cap.

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?

The usage triggers are front-loaded in the first sentence, followed by mechanism, then output states, then exclusions — a logical order. It is a single dense paragraph, and a few clauses (full registry enumeration, marketplace name list) are longer than strictly needed, but nearly every sentence carries actionable information.

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?

With no output schema, the description fully compensates by enumerating every return status and the metadata returned for taken domains (registration/expiry dates, days to expiry, registrar, status codes, nameservers). Combined with the per-call limit and the explicit capability gaps, an agent has everything needed to call and interpret it correctly.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an increment by showing the two accepted call shapes as JSON and clarifying the interaction between names and tlds (each name is checked against every ending), plus the default ending list. It does not add much beyond the schema on individual parameter syntax because the schema already covers it.

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?

The opening sentence names a specific action (check whether a domain is available to register) and the title/description pin down the mechanism: a live per-TLD RDAP registry lookup. It enumerates exactly the outputs (available, registered, registered_expiring, likely_available, unknown, invalid) so an agent knows precisely what the tool produces.

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?

It gives concrete invocation triggers in quotes ("is the .com taken", "domain available", "which of these names has a free domain") and a decision rule: call it before presenting name ideas as available rather than guessing. There are no siblings to route between, and it also states what the tool cannot determine (prices, premium/reserved, trademarks, social handles), which functions as a when-not-to-use boundary.

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