Just Domain

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 self-service: the owner checks it and pays at https://justdomain.ai/transfer, pasting the authorization code there, and a transfer that does not complete is refunded in full. This tool tells the user whether the domain is eligible to move and what one full term would cost; hand over transfer_url, which opens that page for this domain in the owner's browser. Nothing is paid or ordered inside the chat. 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 does not return, accept, or hint 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. 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

Name	Required	Description	Default
`domain`	Yes	One 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

Name	Required	Description
`tld`	Yes
`price`	No	Null when the registrar's price list could not be read. Never estimate a domain transfer price yourself.
`ready`	Yes	TRUE 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.
`domain`	Yes
`source`	Yes	Which public sources actually answered on this request.
`blockers`	No	What stands between this domain and a transfer, most blocking first. An EMPTY list is the only thing that means ready.
`next_step`	Yes	One sentence you can say to the user about what happens next, already matched to this domain's state.
`registrar`	Yes	Who sponsors the domain today, as the REGISTRY reports it.
`supported`	Yes	Whether Just Domain can accept this ENDING at all. Says nothing about this particular domain - read `blockers` for that.
`checked_at`	Yes	ISO-8601 instant these facts were read.
`nameservers`	No
`transfer_url`	Yes	The page on justdomain.ai a PERSON opens in a browser to take this further. The handoff out of the chat.
`dns_continuity`	Yes	Does 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_policy`	Yes	Constant. 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.

Changed1 schema field changedOct 25, 2026

changedOutput schema / properties / blockers / items / properties / code / description

Previous value: -"Stable code: 'locked', 'within_60_days', 'redemption', 'expired', 'tld_unsupported', 'premium', 'not_registered', 'pending_transfer', 'pending_delete', or 'unknown'. If you do not recognise a code, render `detail` verbatim - never drop a blocker you have no wording for."New value: +"Stable code: 'locked', 'within_60_days', 'redemption', 'expired', 'tld_unsupported', 'premium', 'not_registered', 'pending_transfer', 'pending_delete', 'dns_plan_unavailable', or 'unknown'. If you do not recognise a code, render `detail` verbatim - never drop a blocker you have no wording for."

AddedSep 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds extensive behavior beyond annotations: public RDAP and price-list sources only, no authentication, no account reads, and nothing ordered or changed. It explains blockers semantics, unknown codes, RDAP failure meaning, total-term pricing, .ai two-year terms, projected expiry, self-service transfer flow, and strict no-auth-code/no-unlock limits.

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?

Front-loads purpose and safety, and most sentences carry operational meaning. It is somewhat long and repeats the no-payment/no-auth-code boundary, but the repetition is mostly security-relevant for a transfer tool.

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?

Complete for a read-only precheck with an output schema: it explains the critical returned fields (`blockers`, `source.rdap`, `price`, `term_note`, `expected_new_expiry`, `transfer_url`) and the self-service boundaries. An agent has enough context to call and present results correctly.

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 coverage is 100%, and the schema already explains that `domain` must be one fully-qualified domain, not a bare label or list. The description reinforces ownership context but adds little syntax or format detail 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?

States a specific verb and resource: a read-only transfer precheck for ONE domain the user already owns at another registrar. It also clarifies scope and outcome, distinguishing it from search or trademark siblings without needing their schemas.

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?

Gives a clear usage context: one already-owned domain at another registrar, with eligibility, blockers, cost, and DNS survival. It does not explicitly name when to use search_domains or check_trademark instead, so it falls short of full alternative routing.

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

All Just Domain tools Inspect

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.