Skip to main content
Glama

Add a Custom Domain

varity_domain_add
Idempotent

Point your own domain or subdomain at a deployed app and receive the exact DNS record to add at your registrar, then verify domain ownership.

Instructions

Point the user's own domain (e.g. app.example.com or example.com) at a deployed app. Returns the exact DNS record to add at their domain registrar, in plain words. Then call varity_domain_verify.

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": {
      "deployment": "<deployment>",
      "hostname": "<hostname>"
    },
    "name": "varity_domain_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesThe domain or subdomain, e.g. app.example.com.
deploymentYesThe deployment id or app name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (non-read-only, idempotent, non-destructive, open-world), so the description's job is to add context — and it does, stating that the call returns the exact DNS record for the registrar and that verification is a separate follow-up call. It stops short of saying what happens if the hostname is already claimed or whether anything must be propagated before verification succeeds.

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?

Three short sentences, front-loaded with the action, then the return value, then the follow-up call. Every sentence carries distinct information and nothing is repeated from the schema.

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?

There is no output schema, so the description usefully discloses the return content (a plain-words DNS record) and the required follow-up with varity_domain_verify. For a two-parameter, idempotent mutation this is nearly complete; only failure/edge behavior for duplicate or invalid hostnames is unaddressed.

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 description coverage is 100%, with both 'hostname' and 'deployment' documented and patterned in the schema itself, so the baseline is 3. The description restates the hostname example but adds no meaning for the 'deployment' parameter (whether an app name versus a deployment id matters, or which one to prefer), leaving semantics to 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 a specific verb and resource: 'Point the user's own domain ... at a deployed app.' It gives concrete examples of both apex and subdomain forms and immediately distinguishes itself from the sibling it hands off to (varity_domain_verify), so an agent can tell what this tool does without opening the schema.

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?

Usage is clearly framed as part of a two-step flow: call this to get the DNS record, then call varity_domain_verify. That explicit next-step routing is strong guidance, but there is no exclusion guidance — nothing tells the agent when not to use it (e.g., an existing domain that should be removed via varity_domain_remove, or an already-attached hostname).

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