Just Domain
Server Details
Search domain availability and pricing, straight from chat — then open a link to register.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.7/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The single tool has a clear and distinct purpose.
The single tool name 'search_domains' follows a clear verb_noun pattern that is consistent and predictable.
The server only has one tool, which is too few for a domain management context. Users likely need additional operations like registration or renewal, making the tool surface feel thin and incomplete.
The server only provides read-only availability lookup. It lacks any write operations (e.g., purchase, update) or additional queries (e.g., WHOIS, suggestions), leaving significant gaps for most domain-related workflows.
Available Tools
1 toolsearch_domainsSearch domain availabilityARead-onlyIdempotentInspect
Read-only availability and pricing lookup for specific domain names. No purchase or order is created by this tool — it only returns information. Accepts 1–200 fully-qualified domains (e.g. ['acme.com', 'acme.io']) and returns results for exactly those domains — it does NOT suggest alternative TLDs or expand the list. Each result includes whether the domain is available, whether it is a premium name, the first-year registration price, and the annual renewal price. Available results also carry a checkout_url the user can open in a browser to register the domain on justdomain.ai if they choose to.
| Name | Required | Description | Default |
|---|---|---|---|
| domains | Yes | Fully-qualified domains to check, e.g. ['acme.com', 'acme.io', 'acme.ai']. Each entry must include the TLD. Maximum 200 per request. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Set when the search could not be completed (e.g. invalid query, provider failure). |
| domains | Yes | The exact domains requested by the caller, echoed back. |
| results | Yes | |
| warnings | No | |
| next_action | No | |
| error_message | No | |
| component_hint | No |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description reinforces this by stating no purchase is created, and adds valuable behavioral details such as each result including availability, premium flag, prices, and a checkout_url for available domains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with two paragraphs, front-loading the main purpose. Every sentence adds value, though the structure could be slightly more streamlined.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists, the description doesn't need to explain return values. It covers input format, constraints (max 200), and details of each result (availability, premium, prices, checkout_url), making it fully informative.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%. The description adds meaning beyond the schema by providing examples ('e.g. ['acme.com', 'acme.io']') and clarifying that each entry must include TLD, and the maximum count. This helps the agent understand the exact input format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Read-only availability and pricing lookup for specific domain names,' with a specific verb and resource. It distinguishes from purchase tools by explicitly stating 'No purchase or order is created by this tool.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains it accepts 1–200 fully-qualified domains and returns results for exactly those, no suggestions. While there are no sibling tools, it implicitly defines when to use it for checking availability and pricing, but could be more explicit about when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!