Skip to main content
Glama
Sign In

BorealHost

by ai.borealhost
OverviewDiscussionsAdmin

transfer_out_domain

Prepare a domain to transfer to another registrar.

Unlocks the domain and emails the EPP/auth code to the registrant contact on file (BorealHost never sees the code). The domain keeps working here until the transfer completes.

Requires: API key with write scope.

Returns: {"domain", "unlocked": true, "auth_code_emailed": true, "message"}

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": {
      "domain_name": "<domain_name>"
    },
    "name": "transfer_out_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description goes beyond minimal disclosure by explaining the exact side effects: unlocking the domain, emailing the auth code to the registrant, noting BorealHost never sees the code, and confirming the domain remains functional until transfer completes. With no annotations provided, the description adequately carries the transparency burden.

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 compact and well-structured, with the purpose stated in the first line followed by concise bullet-like details. It avoids redundancy and every sentence contributes useful information.

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?

The tool has only one parameter and no output schema, but the description covers the action, side effects, requirements, and return structure. It lacks only minor details such as error scenarios or transfer timelines, but for the tool's complexity it is largely complete.

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

Parameters2/5

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

The schema has 0% description coverage, and the description does not explicitly explain the domain_name parameter format or constraints. The parameter is inferable from the tool purpose, but the description adds no semantic detail beyond the parameter name itself.

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 first sentence 'Prepare a domain to transfer to another registrar' clearly states the tool's purpose with a specific verb and resource. The subsequent details about unlocking and emailing the auth code further clarify its function, distinguishing it from domain management tools like domain_settings or register_domain.

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 implies the use case by stating 'Prepare a domain to transfer to another registrar' and mentions the requirement for write-scope API key, but it does not explicitly discuss when not to use it or name alternative tools. Given the absence of sibling transfer tools, the context is sufficient but not fully explicit.

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

All BorealHost 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