Skip to main content
Glama

Orivox AI Website Builder

by org.orivox
OverviewDiscussionsAdmin

connect_external_domain

Connect a domain the user ALREADY OWNS to their Orivox website -- entirely from this chat, no Orivox dashboard visit needed.

Use this when the user has a domain registered ANYWHERE (their own Name.com account, GoDaddy, a local registrar...) and wants their site on it. This is NOT the buying flow -- for a new domain use search_domains / get_domain_purchase_link instead. Needs an active plan with a free domain slot (the same gate as publishing to a purchased domain).

First call (started=true): Orivox registers the hostname and returns dns_instructions -- ONE DNS record the USER must add wherever their domain's DNS is managed. Present it as a clear table (type / name / value), tell them the registrar/nameservers fields say where their DNS lives when detected, and that adding the record is their only step -- everything else is automatic. Claude cannot add the record for them: Orivox has no access to their registrar account.

After the user says the record is added (or on a later visit): call this SAME tool again with the same arguments. Re-calling IS the activation step -- when the DNS is seen and the certificate is issued (is_active=true), the domain goes live and a never-published site is published automatically; no publish_website call is needed. Do NOT poll repeatedly in one turn: DNS changes take minutes to hours to propagate, so check once and tell the user to come back. A pending status is normal at first; the response's nameservers field helps diagnose a record added at the wrong DNS host. The site stays reachable on its free Orivox subdomain the whole time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
project_guidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so thoroughly: it discloses that Orivox cannot modify the user's registrar account, that re-calling the tool acts as the activation step, that a never-published site may be published automatically, that DNS propagation can take time, and that the site remains available on its subdomain throughout.

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?

Although longer than many descriptions, every sentence earns its place: purpose, prerequisites, first-call behavior, second-call activation, polling guidance, and edge-case diagnosis. The information is front-loaded and organized into logical workflow sections with no filler.

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?

The description fully covers a complex multi-step workflow: prerequisites, DNS instructions, user action, re-invocation as activation, automatic publishing, propagation delays, and troubleshooting via nameservers. Even though the output schema content is not visible, the description references the key output fields (dns_instructions, started, is_active, nameservers) and provides enough context for correct invocation.

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?

Schema description coverage is 0%, so the description must compensate. It does add meaning to 'domain' (an already-owned domain, not a purchase), but it never explicitly explains 'project_guid' or its role as the identifier of the target Orivox website. Only one of the two required parameters receives meaningful semantic enrichment.

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 a specific verb and resource: connecting a domain the user already owns to their Orivox website. It clearly distinguishes itself from the buying flow and names the alternatives (search_domains / get_domain_purchase_link), so an agent can select it correctly among siblings.

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?

It explicitly states when to use the tool ('Use this when...'), when not to use it ('This is NOT the buying flow'), and names the alternative tools for the excluded case. It also gives precise workflow guidance: call once to get DNS instructions, then call the same tool again after the user adds the record—and warns against repeated polling.

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

All Orivox AI Website Builder 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