Skip to main content
Glama

add_custom_domain

Connect apex and/or www on a paid plan; starts a DNS connect session.

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": {
      "site": "<site>"
    },
    "name": "add_custom_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug, e.g. acme-studio
hostsNo1–2 hostnames: apex (example.com) and/or www (www.example.com).
domainNoBare domain when hosts omitted (apex + www); a subdomain connects as-is.
contextNoWhy you're calling this (activity log).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Bare domain when hosts omitted — apex expands to apex + www; a subdomain connects as-is."New value: +"Bare domain when hosts omitted (apex + www); a subdomain connects as-is."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."New value: +"Why you're calling this (activity log)."
  3. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"One sentence: why you are calling this tool and what you are trying to accomplish. Stored on the site's activity log and visible to everyone on the site — never put secrets or personal data here."New value: +"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."
    • removedInput schema / properties / guestToken
      Removed value: -{
      -  "description": "Guest token from start_site. Send it on every call until claim_site. Omit when this chat is already signed in to Dotsy.",
      -  "minLength": 20,
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "context"
      -]New value: +[
      +  "site"
      +]
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the paid-plan prerequisite and that this only opens a DNS connect session rather than completing verification — important behavioral context for a non-idempotent, externally-facing operation.

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?

A single compact sentence with the scope and the key constraint front-loaded. Nothing is padded and no sentence fails to earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation that kicks off an asynchronous DNS flow, the description stops at "starts a session" without indicating what the agent should do next (e.g., poll or wait) or what the call returns. Annotations and the 100%-covered schema carry the rest, but the follow-up path is a real gap for a tool of this complexity.

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%, so the schema already explains site, hosts, domain, and context in detail. The phrase "apex and/or www" echoes the hosts/domain semantics but adds no format or precedence detail beyond what the schema states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (connect) and resource (apex and/or www custom domain) and adds that it initiates a DNS connect session, which is more than a restatement of the name. It does not, however, explicitly distinguish itself from siblings like get_custom_domain_connect, refresh_custom_domain, or reapply_custom_domain_oauth, so the agent must infer the boundary.

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

Usage Guidelines3/5

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

"on a paid plan" supplies a genuine prerequisite, and "starts a DNS connect session" hints this is the entry point of a multi-step flow. There is no explicit when-not guidance and no named alternative for the follow-up step or for re-connecting an already-added domain, leaving usage implied rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources