Skip to main content
Glama

Just Domain

by ai.justdomain
OverviewDiscussionsAdmin

Check whether a domain can transfer to Just Domain

check_domain_transfer
Read-only

Read-only transfer precheck for ONE domain the user already owns at another registrar: could it move to Just Domain, what is stopping it, what would it cost, and does its DNS survive the move. Nothing is ordered, charged, unlocked, or changed. The answer is built from two public sources only, the registry's own RDAP record and our registrar's price list, so it is safe to call without authentication and it reads nothing about the user's account. Read blockers before you say anything: an EMPTY list is the only thing that means the domain is ready to move. Every entry carries a plain detail sentence you can show as-is, and a code you do not recognise must still be reported through its detail rather than dropped. source.rdap: false means the registry did not answer, so nothing about the domain was established: say that, and never call it ready. price is the TOTAL for one full transfer term, not a per-year rate. A .ai transfer adds and charges TWO years because its registry works in two-year units. Do not divide or multiply the amount by a number of years, and do not label it per year; quote term_note beside it. expected_new_expiry is a projection (the registry's current expiry plus the term), not a date any registry has confirmed, so present it as expected. Moving a domain IN is not a self-service function yet. This tool tells the user whether the domain is eligible to move and what one full term would cost; the move itself is arranged by a person, starting at transfer_url and routed through support@just-done.ai. Do not promise what that page will do, and do not describe a payment step for it. Moving a domain OUT of Just Domain IS self-service, and that means a human owner signed in on justdomain.ai in a browser, switching the transfer lock off and issuing the code from their own account. It does not mean you can do it. This tool never returns, accepts, or hints at an authorization (EPP) code, and there is no agent path to unlocking a domain or to having a code issued, here or through any other Just Domain surface, ever. An auth code is a bearer credential for the domain and a chat transcript is not a place to put one. Do not ask the user for a code, do not offer to hold or relay one, and never claim you can unlock or move the domain yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesOne fully-qualified domain the user already owns somewhere else, including its TLD (e.g. 'acme.com'). Not a bare label and not a list: this reads a third-party registry per call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldYes
priceNoNull when the registrar's price list could not be read. Never estimate a domain transfer price yourself.
readyYesTRUE only when `blockers` is empty. It is a convenience over that list and can never disagree with it: anything we could not establish becomes a blocker, so a registry timeout reads as not ready rather than as a green light.
domainYes
sourceYesWhich public sources actually answered on this request.
blockersNoWhat stands between this domain and a transfer, most blocking first. An EMPTY list is the only thing that means ready.
next_stepYesOne sentence you can say to the user about what happens next, already matched to this domain's state.
registrarYesWho sponsors the domain today, as the REGISTRY reports it.
supportedYesWhether Just Domain can accept this ENDING at all. Says nothing about this particular domain - read `blockers` for that.
checked_atYesISO-8601 instant these facts were read.
nameserversNo
transfer_urlYesThe page on justdomain.ai a PERSON opens in a browser to take this further. The handoff out of the chat.
dns_continuityYesDoes the domain's DNS keep working after the move? A transfer moves sponsorship, not DNS, so the current delegation decides whether the site and the mail survive it.
auth_code_policyYesConstant. The rule about authorization (EPP) codes, restated in the payload so it travels with the answer. Follow it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Even with readOnlyHint=true and destructiveHint=false, the description goes well beyond annotations: it states nothing is ordered, charged, unlocked, or changed; explains source.rdap=false means the registry did not answer; clarifies price is total not per-year; and explicitly forbids handling EPP codes. This is exactly the kind of behavioral context an agent needs.

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 long, but every sentence carries an enforceable constraint or interpretive rule: cost, blockers, RDAP absence, expiry projection, human routing, and auth-code handling. It is front-loaded with the core purpose and safety profile before diving into output semantics.

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?

Given that an output schema exists, the description still covers what the schema cannot: how to interpret blockers, code vs detail, source.rdap=false, price term semantics, .ai two-year behavior, expected_new_expiry as a projection, and the no-EPP-code policy. Nothing needed to call and act on this tool correctly is missing.

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?

The schema already documents the single domain parameter fully, including FQDN, ownership elsewhere, and no bare labels/lists. The description re-emphasizes those constraints but does not materially add new parameter-level meaning beyond the 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?

The description opens with 'Read-only transfer precheck for ONE domain the user already owns at another registrar' and enumerates the concrete outputs: could it move, what is stopping it, cost, and DNS survival. This makes the tool's job specific and clearly distinguishable from the sibling search_domains.

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

Usage Guidelines4/5

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

The description clearly frames when to use the tool: for a single domain owned at another registrar, and it explicitly handles the boundary by saying moving a domain IN is not self-service and moving a domain OUT is not what this tool does. It does not explicitly name search_domains as the alternative, but the use case is contextually unmistakable.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources