Skip to main content
Glama
TLDMint MCP Server
by cputop

check_domain_availability

Check live DNS availability for up to 100 domain names in parallel and get verified first-year registration promo codes with direct checkout links.

Instructions

Check live DNS availability for up to 100 specific domain names in parallel and get verified first-year registration promo codes + direct 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": {
      "domains": "<domains>"
    },
    "name": "check_domain_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesList of full domain names to check (e.g. ["vexlo.com", "orbitlab.xyz"]).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses parallel checking, a 100-domain limit, and that results include promo codes and checkout links, but it omits authentication needs, rate limits, error behavior, and what happens when more than 100 domains are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted wording. It efficiently combines purpose, scale, execution style, and return content.

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 simple one-parameter tool, the description covers the input scope and high-level return content. However, because there is no output schema and no annotations, it could say more about the response structure and edge-case behavior.

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 the single domains parameter is already well documented. The description adds the useful maximum of 100 domains, but does not add syntax or format details beyond the schema example.

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?

The description states a specific verb and resource: checking live DNS availability for domain names. It also adds useful scope details (up to 100, in parallel) and return content (promo codes and checkout links), but it does not explicitly distinguish this tool from siblings like get_verified_domain_coupons or inspect_domain_dns_whois.

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

Usage Guidelines2/5

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

The description implies the tool is for checking specific domain names, but it gives no explicit when-to-use guidance, no exclusions, and no comparison to sibling tools. An agent must infer the appropriate context from the name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.