Skip to main content
Glama

Just Domain

by ai.justdomain

Search domain availability

search_domains
Read-onlyIdempotent

Read-only availability and pricing lookup for domain names. No purchase or order is created by this tool; it only returns information. Preferred input: domains, 1 to 200 fully-qualified names (e.g. ['acme.com', 'acme.io']); results cover exactly those domains, with no suggestions or expansion. Fallback input: query, free text (one or more names, comma- or space-separated); names given without a TLD are expanded to popular TLDs (com/io/ai/co/net). Each result includes whether the domain is available, whether it is a premium name, the registration price and the renewal price. Both prices are totals for one full registration term of that ending, not per-year rates: one year on most endings, but two years on .ai, whose registry mandates a two-year term. Do not divide or multiply a returned price by a number of years. Available non-premium results also carry a checkout_url the user can open in a browser to register the domain on justdomain.ai if they choose to. Premium names cannot be registered through Just Domain yet and carry no checkout_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text fallback when exact FQDNs aren't known: one or more names, comma- or space-separated. Names without a TLD are expanded to popular TLDs (com/io/ai/co/net). Ignored when `domains` is provided.
domainsNoFully-qualified domains to check, e.g. ['acme.com', 'acme.io', 'acme.ai']. Each entry must include the TLD. Maximum 200 per request. Preferred over `query`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoSet when the search could not be completed (e.g. invalid query, provider failure).
domainsYesThe exact domains requested by the caller, echoed back.
resultsYes
warningsNo
next_actionNonone
error_messageNo
component_hintNodomain_search_results

TDQS

A5/5.0
Behavior5/5

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

Description adds significant behavioral detail beyond annotations: prices are totals per registration term (not per-year), .ai mandates two-year term, warning not to divide/multiply prices, checkout_url only for available non-premium, premium not registrable. Reinforces read-only and idempotent nature explicitly.

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?

Single paragraph, front-loaded with purpose, then details. Every sentence adds specific, non-redundant information. Efficient and well-structured without fluff.

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?

Covers all critical aspects: availability, premium, pricing semantics, registration term nuances, checkout_url, fallback expansion, and explicit read-only/no-order guarantee. Complete for the tool's complexity, especially with output schema available.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with rich descriptions, and the tool description adds valuable context: 'Preferred over query', exact domain matching, TLD expansion rules for fallback, and maximum limits. Enhances understanding beyond schema.

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?

Clear and specific: 'Read-only availability and pricing lookup for domain names' with explicit statement that no purchase or order is created. Distinct purpose, no ambiguity.

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?

Explicitly states preferred input (domains) and fallback (query), explaining when each is appropriate and what behavior to expect (exact coverage vs TLD expansion). No sibling tools, so no alternative comparison needed; usage context is fully covered.

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

All Just Domain toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A5/5.0
Disambiguation5/5

There is only one tool, so there is no possibility of confusion between tools. The tool's purpose is clearly defined as a read-only domain availability and pricing lookup.

Naming Consistency5/5

With a single tool, naming consistency is trivially maintained. The tool name 'search_domains' follows a clear verb_noun pattern.

Tool Count5/5

The server's sole purpose is to provide domain search information, and a single tool fully fulfills this narrow scope. The count is appropriate and not excessive or insufficient for the apparent domain.

Completeness5/5

The tool comprehensively covers the read-only domain lookup functionality, including availability, premium status, pricing, and checkout URL for non-premium domains. There are no obvious gaps for the stated purpose.

Resources