Skip to main content
Glama

TLDMint Live Domain & DNS MCP

generate_available_domains

Generate niche-tailored domain name ideas (personal email, newsletter, homelab, portfolio, 5-letter brandable, SaaS/AI, domain hacks, e-commerce, etc.) and verify live DNS availability via Cloudflare 1.1.1.1. Returns available domains with first-year promo codes and direct registration checkout links.

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": {
      "keyword": "<keyword>"
    },
    "name": "generate_available_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoSpecialized domain naming algorithm to run.
keywordYesPrimary keyword, brand seed, or first name.
availableOnlyNoWhen true (default), only return domains confirmed available via live DNS check.
secondaryKeywordNoOptional second word, craft/role, or last name (used in personal-email, portfolio, and combiner modes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: live DNS verification via Cloudflare 1.1.1.1, filtering to confirmed-available names, and what the response contains (promo codes, checkout links). It stops short of stating result counts, rate limits, or an explicit read-only/no-side-effect guarantee, which is what would push this to a 5.

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?

Two sentences, front-loaded with the core action and its distinguishing verification capability. The long parenthetical mode list is information-dense rather than redundant, though it could be trimmed without loss.

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 a 4-parameter generation tool with no output schema and no annotations, the description covers the mechanism, the availability filter, and the shape of the return value. Remaining gaps (how many names are produced, whether results are cached or deterministic) are modest for this tool's complexity.

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 description coverage is 100%, so mode, keyword, availableOnly, and secondaryKeyword are already documented with enums and roles. The description reinforces the niche concept behind mode and the availability filter, but adds no syntax, format, or fallback behavior beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb (generate) and resource (domain name ideas), enumerates the niche modes, and adds that it verifies live DNS availability and returns promo codes plus checkout links. That distinguishes it from a pure availability checker, but it never explicitly names check_domain_availability or get_verified_domain_coupons, despite overlapping with both, so the boundary is inferred rather than stated.

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?

Usage is implied by the mode list (pick a mode matching your niche), but there is no explicit when-to-use/when-not statement and no guidance on choosing this tool over check_domain_availability or the coupon tool. The availableOnly default is mentioned only indirectly via 'Returns available domains'.

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.