Skip to main content
Glama

Domains

domains
Read-only

Find domain names and the extensions that fit a business. Returns, by mode, name ideas with prices, extensions that fit with reasons, one name across extensions, availability for a list of domains, prices per extension, or the extension catalog. Use to name a business or check domains before buying one; it never registers or buys a domain. For facts about a domain that is already live use site-intel. mode decides which fields apply: company_name and description for the suggest modes, query for search-extensions, domains for check-availability, tlds for pricing. Cost: suggest-names 5 credits, suggest-extensions 3 credits, search-extensions 2 credits, check-availability 1 credit, pricing 1 credit, tlds 1 credit, charged only when a call succeeds.

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

Input Schema

NameRequiredDescriptionDefault
modeNoWhich domain capability to run.suggest-names
tldsNoExtensions to price (pricing), to check the name across (search-extensions), or to restrict name ideas to (suggest-names).
queryNoAn exact name to check across extensions (search-extensions).
offsetNosearch-extensions: pagination offset into the catalog.
domainsNoFull domains to check, e.g. ["brewhaven.com"] (check-availability).
purposeNoWhat the domain is for (suggest-names / suggest-extensions): website (the site address), cold (a dedicated cold-email domain, kept apart from the site), alias (a site of its own on this address, served from the company's code) or extra (parked: registered, nothing runs on it). Context the model weighs when judging fit; it sets no search options, which are yours to choose (search_options) from what the company needs.
company_idNoOptional O-mega/Founden company id; pulls the real business brief to ground the fit.
descriptionNoWhat the business does; grounds the fit (suggest-* modes).
company_nameNoThe business name (suggest-extensions), or for suggest-names a natural-language brief: any ordering or limit it states (for example "shortest" or "renewal under $15") is read and applied beneath your explicit search_options.
search_optionsNoSearch options, only the fields you set (suggest-names / search-extensions / suggest-extensions): priorities (objective keys in priority order: total_length, annual_price, renewal_price, registration_total, semantic_fit, brandability, label_length), max_total_length and max_label_length (characters), max_annual_price, max_renewal_price and max_registration_total (USD), hacks (include, exclude or only) and allow_premium (boolean). A field you set wins over what the company_name brief asks for; null (or priorities: []) leaves that field to the brief; unknown keys are rejected. Options that do not apply to a mode are ignored there. The response echoes the effective options (search-extensions: search_options; suggest-names: search_plan.search_options).
exact_extensionNosearch-extensions: check ONLY the typed extension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / purpose / description
      Previous value: -"What the domain is for (suggest-names / suggest-extensions): website (the site address), cold (a dedicated cold-email domain, kept apart from the site) or extra. Context the model weighs when judging fit; it sets no search options, which are yours to choose (search_options) from what the company needs."New value: +"What the domain is for (suggest-names / suggest-extensions): website (the site address), cold (a dedicated cold-email domain, kept apart from the site), alias (a site of its own on this address, served from the company's code) or extra (parked: registered, nothing runs on it). Context the model weighs when judging fit; it sets no search options, which are yours to choose (search_options) from what the company needs."
    • changedInput schema / properties / purpose / enum
      Previous value: -[
      -  "website",
      -  "cold",
      -  "extra"
      -]New value: +[
      +  "website",
      +  "cold",
      +  "alias",
      +  "extra"
      +]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, non-destructive, open-world, but the description adds information annotations cannot carry: a per-mode credit cost table and the billing rule 'charged only when a call succeeds.' It also repeats the non-mutating guarantee in concrete terms ('never registers or buys a domain') and previews the return content for each mode, which matters since there is no output schema.

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 purpose, then returns, then alternative, then field mapping, then cost — a sensible priority order. It is a single dense block, and the six-fold return enumeration plus the credit list makes it long, but nearly every clause carries decision-relevant information.

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 an 11-parameter, multi-mode tool with a nested search_options object and no output schema, the description covers mode selection, cost, return content, and the sibling boundary. Remaining gaps are minor: pagination behavior for search-extensions and the meaning of the premium/allowed-hacks flags are left to the schema.

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; this clears it by supplying cross-parameter semantics the schema cannot express per-field, namely the mode-to-field applicability matrix and the precedence rule that an explicit search_options field overrides a constraint stated in company_name. It leaves offset and exact_extension entirely to the schema, so it is not fully complete.

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 first sentence states a specific verb and resource ('Find domain names and the extensions that fit a business') and then enumerates what each of the six modes returns, so the multi-mode surface is legible up front. It also explicitly quarantines the sibling case with 'For facts about a domain that is already live use site-intel,' which is exactly the differentiation an agent needs.

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 positive usage ('name a business or check domains before buying one'), a boundary ('it never registers or buys a domain'), and a named alternative with the condition that selects it ('site-intel' for live domains). It also states which parameters apply to which mode, which is the practical when-to-use question for a mode-switched tool.

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.