Skip to main content
Glama

Set launch page address

launchpad_domain_set

Show the launch page at the business's own subdomain, like join.yourbusiness.com (never a bare domain like yourbusiness.com). One address per workspace. Ask the person first and pass confirm: true after their yes. Returns the one CNAME record they add at their DNS host and the status (waiting_dns, securing, live, error). Their DNS is theirs: never ask for a DNS login. Returns not_available while the feature is off. Requires API key scope: draft.

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": {
      "hostname": "<hostname>",
      "confirm": "<confirm>"
    },
    "name": "launchpad_domain_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYestrue only after the person approved using this address.
hostnameYesThe subdomain, like join.yourbusiness.com.

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?

Beyond the annotations (readOnly=false, idempotent=false, openWorld=true), the description discloses the return payload (one CNAME record plus status), the full status vocabulary, the auth scope required, and the not_available error state. It also adds an operational constraint the annotations cannot express: never ask for a DNS login because the DNS is the customer's.

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?

The key constraint (subdomain, one per workspace) is front-loaded and each sentence carries a distinct fact: approval, return shape, DNS ownership, availability, scope. It is dense but not padded; only the repeated emphasis on 'never a bare domain' is slightly redundant with the example.

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?

With no output schema and a two-parameter write tool, the description covers everything an agent needs: the confirmation protocol, the input format, the returned DNS record and status values, the feature-off case, and the required API key scope. Nothing material is left to inference.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns more by explaining the semantic condition behind confirm (approval must come first) and the format rule for hostname (a subdomain such as join.yourbusiness.com, never an apex domain). These are usage constraints that the schema's minLength/maxLength fields do not convey.

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 and resource ('Show the launch page at the business's own subdomain') and constrains scope with 'One address per workspace', which separates it from the general domain_* siblings. It stops short of naming an alternative or counterpart tool, so the differentiation is implied rather than explicit.

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?

It gives an explicit precondition ('Ask the person first and pass confirm: true after their yes'), a hard exclusion ('never a bare domain like yourbusiness.com'), and a feature-gate caveat ('Returns not_available while the feature is off'). It does not point at launchpad_domain_remove or domain_verify for related cases, but the guidance on when this tool is appropriate is clear.

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